Manage policy database credentials

By default, the PingAuthorize Policy Editor stores policies in an H2 database file on the server. You can set the initial credentials and change them later.

These instructions don’t apply if you are using a managed RDBMS, such as PostgreSQL, instead of the default H2 database.

This embedded H2 file, stored in the server root by default, contains two user accounts:

An admin user: Setup uses the admin user to perform database upgrades.
An application user: The server uses the application user to access the database at runtime.

Each user has its own credentials.

If you change either of the default policy database credentials, you must pass the new credentials to setup when upgrading the server. Otherwise, the setup tool either cannot upgrade the policy database and fails (if neither default credentials work) or resets the changed credentials back to their defaults (if one of the credential pairs works).

For more information about upgrades, see Upgrading PingAuthorize.