Upgrading the PingAuthorize Policy Editor manually - PingAuthorize - 9.1

PingAuthorize

bundle
pingauthorize-91
ft:publication_title
PingAuthorize
Product_Version_ce
PingAuthorize 9.1
category
ContentType
Product
Productdocumentation
paz-91
pingauthorize
ContentType_ce
Product documentation

If you originally installed the PingAuthorize Policy Editor using .zip files, use this procedure to upgrade the Policy Editor when a new version is released.

  1. In your current Policy Editor, complete the steps in Backing up policies.
  2. Stop the Policy Editor.
    $ bin/stop-server
  3. Obtain and unzip the new version of the PingAuthorize Policy Editor in a location outside the existing Policy Editor's installation.
  4. Prepare the existing policy database.
    Note:

    The new server installation might require changes to the policy database structure.

    • If you store your policies in the H2 policy database, copy the existing database. The server setup tool performs these upgrades and generates a new configuration.xml file.

      This example assumes the old installation is in /opt/pingauthorize/PingAuthorize-PAP-previous, and the new installation is in /opt/pingauthorize/PingAuthorize-PAP.

      To upgrade a database from Run this command
      8.1 and later versions
      $ cp /opt/pingauthorize/PingAuthorize-PAP-previous/Symphonic.mv.db opt/pingauthorize/PingAuthorize-PAP
      
      8.0 and earlier versions
      $ cp /opt/pingauthorize/PingAuthorize-PAP-previous/admin-point-application/db/Symphonic.mv.db opt/pingauthorize/PingAuthorize-PAP
      
    • If you store your policies in a PostgreSQL database, follow the steps for Upgrading a PostgreSQL policy database.

  5. Run setup.
    Note:

    Updating PingAuthorize Server uses an update tool. PingAuthorize Policy Editor does not have this tool though. Instead of updating the Policy Editor in-place, you install the new Policy Editor.

    Warning:

    The setup tool uses the default credentials to upgrade the H2 policy database. If the credentials no longer match the default values, the server administrator should pass the correct credentials to the setup tool using the --dbAdminUsername, --dbAdminPassword, --dbAppUsername, and --dbAppPassword command-line options. Otherwise, setup fails when it cannot access the H2 policy database, or it might reset credentials to their default values. For more information, see Manage policy database credentials.

    Follow the instructions in one of the following topics:

  6. Start the new Policy Editor.
    Follow the instructions in Post-setup steps (manual installation).
  7. In the new Policy Editor, complete the steps in Upgrading the Trust Framework and policies.