Using setup or environment variables, you can set credentials for both the admin user and the application user.

Because this setup is an initial setup, the Policy Editor is not running.

  • Set credentials for both the admin user and the application user.

    • Setting credentials with the setup tool.

      Include the following options and the credential values with setup:
      • --dbAdminUsername
      • --dbAdminPassword
      • --dbAppUsername
      • --dbAppPassword
      For example, the following command sets the policy database admin credentials to adminuser / Passw0rd and the policy database application credentials to appuser / S3cret.
      bin/setup --dbAdminUsername adminuser \
  --dbAdminPassword Passw0rd \
  --dbAppUsername appuser \
  --dbAppPassword S3cret \
  --interactive

    • Setting credentials with environment variables.

      Using environment variables, you can avoid credentials showing up in process lists and command-line history.

      The following example sets the policy database admin credentials to adminuser / Passw0rd and the application user credentials to app / S3cret.
      env PING_DB_ADMIN_USERNAME=adminuser \
  PING_DB_ADMIN_PASSWORD=Passw0rd \
  PING_DB_APP_USERNAME=app \
  PING_DB_APP_PASSWORD=S3cret \
  bin/setup

      Using environment variables at initial setup generates the configuration.yml file with the adminuser / Passw0rd credentials and the app / S3cret credentials instead of the default credentials.

      For more information about these and other UNIX environment variables you can use to override configuration settings, see Starting PingAuthorize Policy Editor.