Changelog
The following is the change history for the X.509 Token Translator.
Updated April 19, 2024.
X.509 Token Translator 1.3.2 – April 2024
-
Fixed an issue that caused the adapter to sometimes fail to redirect users who authenticated successfully back to the primary HTTPS port.
X.509 Token Translator 1.3.1 – September 2021
-
Verified that the X.509 Token Processor is compliant with US Federal Information Processing Standards (FIPS). For usage, see Integrating with Bouncy Castle FIPS provider in the PingFederate documentation.
X.509 Token Translator 1.3 – January 2020
-
Extended the core contract to include the serial number of the client certificate.
-
Added the option to use the client certificate for acceptable issuer validation.
X.509 Token Translator 1.2.1 – March 2017
-
Updated 3rd party library
-
Adapter works with PingFederate authentication policies
X.509 Token Translator 1.2 – November 2016
-
Added ability to customize Authentication Context in saml assertions.
-
Added support for Subject Alternative Name attributes.
-
Added ability to redirect to a host for client-certificate authentication.