Resolved issues

Ticket ID Description


Resolved an issue that caused the audit log to intermittently record incorrect connection IDs.


To reduce the number of search requests to directory servers during user authentication, PingFederate no longer performs multiple calls to the LDAP Root DSE checking for IntermediateClientRequestControl support. This LDAP control can send servers information about a client and any downstream clients.


The OAuth client connection ID is no longer missing from some events in the audit log.


PingFederate with Bouncy Castle FIPS integration now lets you place the Bouncy Castle provider at the top of the provider list in the file. This ensures that PingFederate uses the Bouncy Castle provider for cryptographic signing operations. Before you change the provider ordering in an existing deployment, see "Integrating with Bouncy Castle FIPS provider" in the PingFederate documentation.