PingDirectory

PingDirectory suite of products 10.1.0.4 (September 2025)

Fixed the failure behavior for dsreplication initialize

Fixed DS-49890 PingDirectory

We fixed an issue where a PingDirectory server would continue sending binary data to the destination server after a failed attempt to initialize using dsreplication initialize. This behavior interfered with further initialization attempts from any other server.

Fixed a replace-certificate argument issue

Fixed DS-49769 PingDirectory, PingDirectoryProxy, PingDataSync

We fixed an issue where replace-certificate replace-listener-certificate didn’t obey the --trust-store-update-type argument.

Fixed an issue with some password resets

Fixed DS-50108 PingDirectory, PingDirectoryProxy

We fixed an issue where password resets done with the bypass-pw-policy privilege would circumvent the force-change-on-reset property of password policies.

Excluded some password attributes from sync sources

Fixed DS-49212 PingDataSync

We changed the resync tool to exclude unicodePwd automatically from AD sync sources and password from PingOne sync sources.

By design, the resync tool updates the existing values for included attributes at the destination to match what’s found at the source. If resync can’t retrieve an attribute value at the source, it removes any existing values at the destination. Because resync can’t retrieve these password attributes from their sources, we’ve excluded them from the attributes for resync consideration to avoid disrupting the values at the destination.

You can still include these attributes manually in a resync operation by providing the --includeSourceAttr argument.

Fixed a plugin issue with delete operations

Fixed DS-50377 PingDirectory

We fixed an issue where the Referential Integrity plugin rejected delete operations when the DN of the delete operation was out of scope.

Running an LDIF import as an administrative task

Issue DS-50286 PingDirectory

When you run an LDIF import as an administrative task, the import process doesn’t verify that the source LDIF file exists before clearing the backend.

Before running an LDIF import as an administrative task, do the following:

  • Ensure that the LDIF file exists.

  • Check for typos in the file path or file name.

  • Consider backing up the backend data.

Fixed an issue with the Monitor History plugin preserving files

Fixed DS-46253 PingDirectory, PingDirectoryProxy, PingDataSync

We fixed an issue where the Monitor History plugin wouldn’t preserve files for longer than 14 days when retain-files-sparsely-by-age was set to true.