When upgrading, you must consider factors such as the scope of the update, the PingAuthorize or PingDataGovernance version from which you are upgrading, and if you are not using Docker, your installed version of Java.
The 22.214.171.124 release is the first release of PingAuthorize. Previously, the product was known as PingDataGovernance.
For Docker installations, the upgrade process involves downloading and deploying the latest containers.
For manual installations, the upgrade process involves downloading and extracting a
new version of the PingAuthorize Server
.zip file on the server and running the update utility with
-R option value from the new
root server pointing to the installation.
Consider the following when upgrading:
- If you are upgrading from a PingAuthorize Early Access release to a PingAuthorize General Availability release, you must upgrade both the PingAuthorize Server and the Policy Editor before you use the Policy Decision Service in external mode. Upgrading only one component results in this error: Please upgrade to PingAuthorize Policy Editor version <X.X.X.X>.
- The update affects only the server being upgraded. The process does not alter the configuration of other servers, so you must update those servers separately.
- The update tool verifies that the installed version of Java meets the new server requirements. To simplify the process, install the version of Java that is supported by the new server before running the tool.
- Upgrades for PingDataGovernance Server are only supported from versions 126.96.36.199 or later. If upgrading from a version of PingDataGovernance prior to 188.8.131.52, configuration loss will occur. The update tool has a warning message about this.
For additional considerations, see Planning your upgrade.
For information about important fixes made over several releases, see Critical Fixes.
Considerations introduced in PingAuthorize 184.108.40.206
Keep in mind the following important upgrade considerations introduced in this version of PingAuthorize Server.
Peer server setup has been removed. To manage server configuration, use server profiles instead of peer setup. Server profiles support deployment best practices such as automation and Infrastructure-as-Code (IaC). For more information about server profiles, see Deployment automation and server profiles.