Example: Set up the PingAuthorize Policy Editor with a PostgreSQL policy database

This example sets up the PingAuthorize Policy Editor in demo mode with the following options:

Automatically generated self-signed server certificate
PostgreSQL policy database with server runtime credentials (see the following caution about --dbAppPassword)

$ bin/setup demo \
  --dbConnectionString "jdbc:postgresql://<host>:<port>/<database>" \
  --dbAppUsername "<db-user>" \
  --dbAppPassword "<db-password>" \
  --generateSelfSignedCertificate \
  --decisionPointSharedSecret pingauthorize \
  --hostname  <pap-hostname>  \
  --port  <pap-port>  \
  --adminPort  <admin-port>  \
  --licenseKeyFile  <path-to-license>

Using the --dbAppPassword option to provide the PostgreSQL database password to the setup tool persists the password to a configuration file.

Instead, omit --dbAppPassword entirely to persist the default password, and set the PING_DB_APP_PASSWORD environment variable before server start. For example:

$ env PING_DB_APP_PASSWORD=<db-password>  bin/start-server