The release notes for the 8.3.0.6 release of PingDirectory Server.
Critical fixes
This release of the Directory 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 PingDirectory Server.
Ticket ID | Description |
---|---|
DS-40796 |
To enhance initialization performance, the |
DS-41468 |
Fixed an issue that prevented the server from refreshing the monitor data used to detect and warn about an upcoming certificate expiration. This could cause the server to continue to warn about an expiring certificate even after that certificate had been replaced. |
DS-45162 |
Added support for new extended operations that can be used to help manage the server's listener and inter-server certificates. Updated the replace-certificate tool to add support for replacing and purging certificates in a remote instance, and to allow skipping validation for the new certificate chain. |
DS-45449 |
Updated the server to create the esTokenizer.ping file if it does not exist for a backend containing encrypted data. This file may be needed to open the database environment for a backend containing encrypted indexes, but it would not have been automatically created when upgrading from a pre-7.0 server to a later version with support for encrypted indexes. |
DS-45480, DS-45636 |
|
DS-45647 |
Resolved an issue where SCIM POST requests that violated a unique attribute constraint got an internal error instead of the expected SCIM error response. |
DS-45786 |
Fixed a PingDirectory server issue that could cause an internal error to be logged while monitoring database statistics for read-only backends. |
DS-45788 |
Fixed an issue where the Directory Rest API returns an HTTP 500 error response
when trying to retrieve a SCIM entry whose corresponding LDAP entry contains a
valid Generalized Time Syntax attribute value not matching the specific format
|
DS-45815 |
Updated PingDirectory products to use Kafka v2.8.1 which resolves CVE-2021-38153. |