Define policy configuration keys in a development environment - PingAuthorize

Define policy configuration keys in a development environment - PingAuthorize - 9.1

PingAuthorize

bundle

pingauthorize-91

ft:publication_title

PingAuthorize

Product_Version_ce

PingAuthorize 9.1

category

ContentType

Product

Productdocumentation

paz-91

pingauthorize

ContentType_ce

Product documentation

Before you can use any policies that you developed with the Consent API policy information provider (PIP), you must configure the Policy Editor to provide values for the PIP’s base URL, username, and password.

To configure the Policy Editor to provide these values, re-run the setup tool using an options file to generate a new configuration, as shown in the following steps.

Make a copy of the default options file.
```
$ cp config/options.yml my-options.yml
```

Edit the new options file and define the policy configuration keys in the core section.

core:
  ConsentBaseUri: https://consent-us-east.example.com/consent/v1
  ConsentUsername: cn=consent admin
  ConsentPassword: Passw0rd123
# Other options omitted for brevity...

Stop the Policy Editor.
```
$ bin/stop-server
```

Run setup using the --optionsFile argument, and then customize all other options as appropriate for your needs.

$ bin/setup demo \
 --adminUsername admin \
 --generateSelfSignedCertificate \
 --decisionPointSharedSecret pingauthorize \
 --hostname <pap-hostname> \
 --port <pap-port> \
 --adminPort <admin-port> \
 --licenseKeyFile <path-to-license> \
 --optionsFile my-options.yml

Start the Policy Editor.
```
$ bin/start-server
```