This upgrade moves to Jetty 9.4. As a result, the HTTPS connection handler will no
longer support TLS_RSA ciphers by default. If you use any legacy HTTPS clients that
still require TLS_RSA ciphers, modify the
of the HTTPS Connection Handler to include them.
Peer setup and clustered configuration are deprecated and will be removed in PingDataGovernance 9.0. If you plan to upgrade to PingDataGovernance 8.0 at some point, consider using server profiles to manage server configuration. Introduced in PingDataGovernance 8.0, server profiles support deployment best practices such as automation and Infrastructure-asCode (IaC). For more information about server profiles, see the PingDataGovernance Server Administration Guide for PingDataGovernance 8.0 or later
The following issues have been resolved with this release of PingDataGovernance Server.
|Fixed an issue that could prevent some tools from running properly with an encrypted tools.properties file.
|Updated the server to make the general monitor entry available to JMX clients.
|Updated the cn=Cluster subtree to prevent clustered configuration changes when servers in the cluster have mixed versions. To make clustered configuration changes, either update all servers in the cluster to the same version, or temporarily create separate clusters by server version by changing the cluster-name property on the server instance configuration objects.
|To avoid inconsistencies, changing clustered configuration will now require all servers in the cluster to be on the same product version. Servers will not pull any clustered configuration from the master of the cluster if they are on a different product version.
|Fixed an issue with manage-profile replace-profile where certain configuration changes for recurring task chains were not being applied.
|Fixed an issue that prevented password changes for topology administrators unless their password policy was configured to allow pre-encoded passwords.
|Upgrade to Jetty 9.4.30.