Critical fixes

This release of 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 Directory Server.

Ticket ID Description


Added the ability to retry operation failures from replication if the failures are likely due to dependent writes being played out of order. This issue only affected environments that were sending writes to different servers, and also were not able to use the appropriate level of replication assurance. To enable this setting, update the on-replay-failure-wait-for-dependent-ops-timeout configuration property on a replication domain.


Fixed an issue where the format field is omitted from the list of operational attribute schemas in the Directory REST API.


Addressed an issue where the backend would store an incorrect count for a database key that had exceeded the index entry limit. This would only happen for composite indexes when the server started up after not being shut down cleanly. Normal search processing was unaffected, but the matching entry count request control processing would return incorrect results.


Updated the server to allow the operation purpose control to be used for operations that are part of an LDAP transaction.


Fixed an issue that could prevent password policy state changes made through the ds-pwp-modifiable-state-json operational attribute from being properly replicated.