Critical Fixes

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

No critical issues have been identified.

Resolved Issues

The following issues have been resolved with this release of the PingDirectory Server.

Ticket ID Description


Addressed an issue where symmetric keys were not being sanitized in the config-audit.log.


Fixed an issue with the dsreplication tool where baseDNs and restricted baseDNs were improperly handled as case sensitive.


Fixed an issue that caused the encode-password tool to fail when the AES256 password storage scheme is enabled.


Fixed an issue where a replication initialize task that ran longer than the configured connection idle-timeout-limit would cause the initialize to fail.


Fixed an issue that allowed replication protocol messages to be dropped.


Resolved an issue where SCIM POST requests that violated a unique attribute constraint received an error response with status 400 (Bad Request) instead of 409 (Conflict).


Fixed an issue that caused replication enablement to fail if there is at least one topology-wide administrator with no password.


Resolved an issue with slow response time on PingDirectory servers configured with a large number (10,000 or more) of virtual static groups.


The replication server now continues to handle incoming replication connections even when there is an unexpected exception.


Fixed an issue where new servers could not be enabled into a large topology.