PingDS 8.0.0

Before you add new servers

Fulfill these requirements before upgrading PingDS software, especially before upgrading the software in a production environment. Also review the requirements listed in the release notes.

Supported Java

  • Always use a JVM with the latest security fixes.

  • Make sure you have a supported Java environment installed on the system.

    If your default Java environment is not appropriate, use one of the following solutions:

    • Edit the default.java-home setting in the opendj/config/java.properties file.

    • Set OPENDJ_JAVA_HOME to the path to the correct Java environment.

    • Set OPENDJ_JAVA_BIN to the absolute path of the java command.

  • When running the dskeymgr and setup commands, use the same Java environment everywhere in the deployment and refer to CAs from deployment IDs.

DS software supports the following Java environments:

Vendor Versions

OpenJDK, including OpenJDK-based distributions:

  • AdoptOpenJDK/Eclipse Temurin Java Development Kit (Adoptium)

  • Amazon Corretto

  • Azul Zulu

  • Red Hat OpenJDK

Ping Identity tests most extensively with AdoptOpenJDK/Eclipse Temurin.

Use the HotSpot JVM if possible.

21

Oracle Java

21

TLS cipher support depends solely on the JVM. Learn more in TLS settings.

CAs from deployment IDs

Due to a change to the Java platform between versions 11 and 17, the key pairs you generate with the dskeymgr and setup commands using Java 11 are incompatible with keys generated using Java 17 and later.

Running DS servers with incompatible Java versions is a problem when you use deployment ID-based CA certificates.

If you use your own CA, not one derived from a deployment ID, skip this section.

Replication breaks, for example, when you use the setup command for a new server with a more recent version of Java than was used to set up existing servers.

Find troubleshooting suggestions in Overcome incompatible Java versions when adding new servers.

Next steps