Ping Identity Platform

Upgrade

Platform upgrade complexity depends on the deployment. Upgrades for heavily customized deployments using many advanced features require far more care and planning than an upgrade for a sample evaluation deployment.

Make sure you plan and test appropriately before attempting to upgrade a production deployment.

Upgrade process

To upgrade your sample deployment from 7.5 to 8.0, follow these high-level steps:

  1. Upgrade the platform UIs.

    Use the new UIs described in Set up the platform UIs.

  2. Upgrade PingGateway.

    Find more information in Upgrade in the PingGateway documentation.

  3. Upgrade PingDS.

    Find more information in Upgrade in the PingDS documentation.

  4. Upgrade PingAM.

    Find more information in Upgrade in the PingAM documentation.

  5. Upgrade PingIDM.

    Find more information in Upgrade in the PingIDM documentation.

When upgrading from earlier versions of the sample deployment, read the earlier upgrade instructions and Migration and customization.

Changes from 7.5 to 8

  • Use Java 21.

  • Use Tomcat 10 for AM.

  • PingIDM 8 uses Logback to generate its server logs. The default location for the server logging configuration file has changed from conf/logging.properties to conf/logback.xml. Find more information in Server logs in the PingIDM documentation.

Changes from 7.4 to 7.5

  • Use Java 17.

  • The sample deployments now require PingGateway.

    The Platform UI component applications don’t all run on the same host and port. This means cookies and iframes don’t always share the same host and origin, a potential problem for modern browsers.

    PingGateway protects access to the platform and ensures a single host and port for all browser-based interactions.

  • The procedures to configure PingAM now demonstrate how to use PingDS as an external token store.

  • The PingGateway config.json configuration file has changed. PingGateway 2025.3 requires you to declare objects directly in the heap before referencing them.

Changes from 7.3 to 7.4

  • The Amster .zip file Amster-8.0.1.zip now includes a root folder named amster.

  • The Platform UI Docker image version format has changed. For details, refer to Run Docker images.

  • The procedures for configuring PingIDM now include:

    • A new ui-themerealm.json file to enable theming for hosted UI pages.

      This addition makes it possible to edit authentication journeys through the Platform Admin UI.

    • An update to the repo.ds.json file to support password policies with Force Password Change enabled.

      This update adds the following settings to dsconfig/passwordPolicies > properties:

      {
  "allowExpiredPasswordChanges": {
    "type": "simple",
    "ldapAttribute": "ds-cfg-allow-expired-password-changes"
  },
  "expirePasswordsWithoutWarning": {
    "type": "simple",
    "ldapAttribute": "ds-cfg-expire-passwords-without-warning"
  },
  "passwordExpirationInterval": {
    "type": "simple",
    "ldapAttribute": "ds-cfg-password-expiration-warning-interval"
  }
}

      You can find the Force Password Change option in the Platform Admin UI under Security > Password Policy.