Upgrade Consideration

Important consideration for upgrading to this version of PingDataGovernance Server:

  • If you are updating a multi-server topology from PingDataGovernance 7.0.x to, you must use the --skipMirroredSubtreeUpdateTask option for the updater or the update fails. Alternatively, you can uninstall all but one of the servers to retain the base configuration, update the standalone server, install fresh servers on the new version, and add them back to the topology with the peer options. However, using the --skipMirroredSubtreeUpdateTask option is the recommended path.

Critical Fixes

This release of the Data Governance Server addresses critical issues from earlier versions. Update all affected servers appropriately.

  • Addressed an issue that could lead to slow, off-heap memory growth. This only occurred on servers whose cn=Version,cn=monitor entry was retrieved frequently.
    • Fixed in:
    • Introduced in:
    • Support identifiers: DS-41301
  • The following enhancements were made to the topology manager to make it easier to diagnose connection errors:
    • Added monitoring information for all the failed outbound connections (including the time since it ha been failing and the last error message seen when the failure occurred) from a server to one of its configured peers and the number of failed outbound connections.
    • Added alarms/alerts for when a server fails to connect to a peer server within a configured grace period.
    • Fixed in:
    • Introduced in:
    • Support identifiers: DS-38334 SF#00655578
  • The topology manager now raises a mirrored-subtree-manager-connection-asymmetry alarm when a server can establish outbound connections to its peer servers but those peer servers cannot establish connections back to the server within the configured grace period. The alarm is cleared as soon as there is connection symmetry.
    • Fixed in:
    • Introduced in:
    • Support identifiers: DS-38344 SF#00655578
  • Fixed two issues in which the server could have exposed some clear-text passwords in files on the server file system.
    • When creating an encrypted backup of the alarms, alerts, configuration, encryption settings, schema, tasks, or trust store backends, the password used to generate the encryption key (which may have been obtained from an encryption settings definition) could have been inadvertently written into the backup descriptor.
    • When running certain command-line tools with an argument instructing the tool to read a password from a file, the password contained in that file could have been written into the server's tool invocation log instead of the path to that file. Affected tools include backup, create-initial-config, ldappasswordmodify, manage-tasks, manage-topology, reload-http-connection-handler-certificates, remove-defunct-server, restore, rotate-log, and stop-server. Other tools are not affected. Also note that this only includes passwords contained in files that were provided as command-line arguments; passwords included in the tools.properties file, or in a file referenced from tools.properties, would not have been exposed.

      In each of these cases, the files would have been written with permissions that make their contents only accessible to the system account used to run the server. Further, while administrative passwords might have been exposed in the tool invocation log, neither the passwords for regular users, nor any other data from their entries, should have been affected. We have introduced new automated tests to help ensure that such incidents do not occur in the future.

      We recommend changing any administrative passwords you fear might have been compromised as a result of this issue. If you are concerned that the passphrase for an encryption settings definition might have been exposed, then we recommend creating a new encryption settings definition that is preferred for all subsequent encryption operations. You also might want to re-encrypt or destroy any existing backups, LDIF exports, or other data encrypted with a compromised key, and you might want to sanitize or destroy any existing tool invocation log files that might contain clear-text passwords.

    • Fixed in:
    • Introduced in:
    • Support identifiers: DS-38897 DS-38908

Known Issues/Workarounds

The following item is a known issue in the current version of PingDataGovernance Server:

  • The internal SCIM interface in the BrokerContext class of the Server SDK has been deprecated. It will be removed in a future version of the product. Extensions that need to interact with the SCIM service should use an HTTP client SDK or other means.

Resolved Issues

The following issues have been resolved with this release of PingDataGovernance.

Ticket ID Description

Added a logging-error-behavior property to the log publisher, periodic stats logger plugin, and monitor history plugin configuration that you can use to specify the behavior the server should exhibit if an error occurs while attempting logging-related processing. By default, the server preserves its previous behavior of writing a message to standard error; however, you can configure it to enter lockdown mode on a logging error. In this mode, the server reports itself as UNAVAILABLE and only accepts requests from accounts with the lockdown-mode privilege and only from clients communicating over a loopback interface.

DS-40767, DS-41229
Fixed an issue in which a PingDataGovernance Server could return an HTTP 500 error while logging the policy decision response if using these items:
  • External PDP mode
  • The Policy Decision Service with a "decision-tree" decision response view
  • A policy that uses a service with HTTP authentication

Also, the Policy Decision Logger now records external policy decisions to the policy decision log as a single line for easier use with the Policy Administration GUI Log Visualizer.


PingDataGovernance Server no longer prevents a server with an expired license from restarting.


The Policy Administration GUI now includes decision evaluation details in the decision-audit.log by default. With this change, policy writers can visualize decisions by copying and pasting the JSON into the Log Visualizer.


Addressed an issue that could lead to slow, off-heap memory growth. This only occurred on servers whose cn=Version,cn=monitor entry was retrieved frequently.