You can run the PingAuthorize Policy Editor setup command interactively in command-line interface (CLI) install mode.
You must have the following information:
- The location of a valid license file
- An available port for the PingAuthorize Policy Editor to accept HTTPS requests
The setup tool prompts you interactively for the information that it needs.
You cannot configure some setup options when installing the PingAuthorize Policy Editor interactively, such as PostgreSQL database configuration. For more information, see Installing the PingAuthorize Policy Editor non-interactively.
Choose the authentication mode for the PingAuthorize
Demo mode: Configures the PingAuthorize Policy Editor to use form-based authentication with a fixed set of credentials. Unlike OpenID Connect (OIDC) mode, this mode doesn't require an external authentication server. However, it is inherently insecure and should only be used for demonstration purposes.
OIDC mode: Configures the PingAuthorize Policy Editor to delegate authentication and sign-on services to a PingFederate OIDC provider.
In OIDC mode, you must provide the following additional information:
- The host name and port of an OIDC provider
- Information related to the server's connection security, including the location of a keystore that contains the server certificate, the nickname of that server certificate, and the location of a trust store
To use PingAuthorize Policy Editor with other OIDC providers, such as PingOne, see Installing the PingAuthorize Policy Editor non-interactively.
- Run the setup command.
Copy and record any generated values needed to configure external
The Shared Secret is used in PingAuthorize, under .
To start the Policy Editor, or policy administration point
The Policy Editor runs in the background, so you can close the terminal window in which it was started without interrupting it.
- Complete the steps in Post-setup steps (manual installation).
- Consider additional configuration options in Specifying custom configuration with an options file.