Publishing a version
You can publish notable points in Version History to deploy policies and Trust Framework definitions to decision endpoints or to Authorize gateways.
About this task
Publishing a version is like saving a snapshot of your policies and Trust Framework definitions. The published version reflects the state of these objects at a specific point in time.
By default, PingOne Authorize provides three decision endpoints for every environment: Dev, Test, and Prod. You can publish a version to multiple decision endpoints or Authorize gateways, but each decision endpoint can have only one version published to it at a time. The version is replaced each time you publish to an endpoint or Authorize gateway. If an endpoint is set to use the latest version, updated versions are published to it automatically.
Use the following steps to publish versions to decision endpoints. To publish versions to Authorize gateways, go to Publishing policy versions to Authorize gateway instances.
|
Ensure that your policies and Trust Framework definitions are thoroughly tested before you publish them to the Prod endpoint and use them in production. |
Steps
-
Go to Authorization > Version History.
-
Click the More Options (⋮) icon next to the version that you want to publish and select Publish Version.
Do not publish versions with names that begin with API Access Management. Instead, deploy the API service to publish these changes.
-
In the Publish to list, select an endpoint.
-
For version Name, enter a name that makes the version easy to identify.
If there’s already a name, you can keep it or update it. The name is used as a tag in audit events.
-
Click Publish.
Result:
The version name and the endpoints that the version is published to are displayed in Version History.