PingDirectory suite of products 9.3.0.7 (November 2024)
Made it easier to upgrade replicated servers to version 9.3.0.7 or later
Improved DS-48798, DS-49090 PingDirectory
When upgrading a pre-9.2 PingDirectory server in a replicated topology to version 9.3.0.7 or later, the update tool will automatically set replication-purge-obsolete-replicas to false for that server, if not already explicitly configured.
This change helps avoid unintended consequences when upgrading a pre-9.2 replicated server because the replication-purge-obsolete-replicas configuration property has a value of true by default in version 9.2.
After upgrade, the update tool also displays a message with more information:
In the 9.2.0.0 release, the implicit default value for the 'replication-purge-obsolete-replicas' global configuration property changed from 'false' to 'true'. However, it should generally only be set to true if all servers in the topology are at version 9.2.0.0 or later. Because this server is being updated from a pre-9.2.0.0 version, it is possible that there are still other pre-9.2.0.0 servers in the topology. As such, the 'replication-purge-obsolete-replicas' property will be explicitly set to false for this server if it was not explicitly set. Once you have completed the upgrade across all servers in the topology so that there are no more pre-9.2.0.0 replicas, consider manually setting this property to 'true' on all servers.
Fixed a config-diff error
Fixed DS-49071 PingDirectory, PingDirectoryProxy, PingDataSync
Fixed an issue where config-diff would result in an Unknown property error when comparing configuration objects of different types.
Removed the restart prompt when changing a certificate alias
Fixed DS-45174 PingDirectory, PingDirectoryProxy, PingDataSync
Removed the prompt to restart the LDAP connection handler component after changing the ssl-cert-nickname configuration property because a restart isn’t required.
Removed suppression messages for disabled alerts
Fixed DS-49119 PingDirectory, PingDirectoryProxy, PingDataSync
Fixed an issue where alert types that were disabled would still output suppression messages.
Fixed an issue with attribute value types in proxy transformations
Fixed DS-48958 PingDirectoryProxy
Updated the attribute mapping proxy transformation to require that both the source and target attribute types are defined in the local schema. This fix ensures that the server correctly handles those attribute values (for example, when identifying value types and formatting values for return in REST API responses).
The server now prevents you from adding a new attribute mapping proxy transformation if either of the attribute types isn’t defined in the schema. If any existing transformations of this kind reference attributes whose types aren’t defined in the schema, the server logs a warning message on startup.