Upgrading a PostgreSQL policy database - PingAuthorize - 9.3

PingAuthorize 9.3

bundle
pingauthorize-93
ft:publication_title
PingAuthorize 9.3
Product_Version_ce
PingAuthorize 9.3
category
ContentType
Product
Productdocumentation
paz-93
pingauthorize
ContentType_ce
Product documentation

To upgrade an existing PostgreSQL policy database, use the policy-db tool.

  • The PostgreSQL instance must be reachable on the network from the Policy Editor host and listening for connections.
  • The Policy Editor uses both a PostgreSQL administration user and a server runtime user. The administration user must be able to create new databases. Continue to use the same administration user when new releases of the Policy Editor become available to prevent database object ownership issues. Consult the official PostgreSQL documentation for help with creating new database users and for configuring PostgreSQL to listen for remote connections securely.
  • The Policy Editor uses Java Database Connectivity (JDBC) to connect to PostgreSQL. Be prepared to provide the JDBC connection string in the following format: jdbc:postgresql://<host>:<port>/<name>. For example: jdbc:postgresql://example.com:5432/pap_db.

When a newer version of the Policy Editor is released, it will fail to start when pointing to a PostgreSQL database with older database objects. Running start-server will print a message like the following to the console:

The policy database at 'jdbc:postgresql://example.com:5432/pap_db' is older than this version of PingAuthorize Policy Editor (9.2.0.0).
Please use the policy-db tool to upgrade the database before running start-server again.

This message indicates that you must run the policy-db tool for this newer version of the Policy Editor to upgrade the database objects.

Follow these instructions to upgrade a PostgreSQL database for a manual upgrade of the Policy Editor. Be prepared to provide the database administration credentials and server runtime credentials you used to create the PostgreSQL database.

Note:

See Deploying PingAuthorize Policy Editor using Docker for containerized deployments.

  1. Complete steps 1-3 of Upgrading the PingAuthorize Policy Editor manually.
  2. Run the following command:
    $ bin/policy-db \
      --dbConnectionString "jdbc:postgresql://<host>:<port>/<name>" \
      --dbAppUsername <server-runtime-username> \
      --dbAppPassword <server-runtime-password>
    
    Note: Alternatively, you can provide the server runtime password through the PING_DB_APP_PASSWORD environment variable.
  3. Provide the database administration credentials when prompted.
The policy-db tool connects to PostgreSQL and applies the upgrades.

Complete steps 5-7 of Upgrading the PingAuthorize Policy Editor manually.

Important:

Provide the Policy Editor with the same --dbConnectionString, --dbAppUsername, and server runtime password you used to create the PostgreSQL database.