Note: Running the setup tool regenerates the configuration.yml file and regenerates any self-signed certificate keystore.
  1. Stop the Policy Editor. 
    bin/stop-server
  2. Run setup with the options desired from the following set and specify the new credentials. To change from the default credentials, run setup one time. To change from nondefault credentials, run setup combined by double ampersands (&&) with a second setup; in the first command, specify the current credentials for the admin user and the new credentials for the application user, and then in the second command, specify the new credentials for the admin user and the now-current credentials for the application user. See the examples.
    • --dbAdminUsername
    • --dbAdminPassword
    • --dbAppUsername
    • --dbAppPassword
    The first example changes the credentials for the admin and application accounts from their defaults to admin / Passw0rd and app / S3cret, respectively.
    setup --dbAdminUsername admin \
  --dbAdminPassword Passw0rd \
  --dbAppUsername app \
  --dbAppPassword S3cret \
  --interactive
    With the credentials no longer the defaults, to change the credentials, you need two setup commands. The first command uses the current admin credentials (admin / Passw0rd) and sets new application credentials (app and F0cu5). The second command then uses the newly set application credentials (app and F0cu5) to set new admin credentials (admin and S3cure).
    setup --dbAdminUsername admin \
  --dbAdminPassword Passw0rd \
  --dbAppUsername app \
  --dbAppPassword F0cu5 \
  --interactive \
  && setup --dbAdminUsername admin \
  --dbAdminPassword S3cure \
  --dbAppUsername app \
  --dbAppPassword F0cu5 \
  --interactive
  3. Start the Policy Editor. 
    bin/start-server