Changelog

Fixed an issue that caused the adapter to sometimes fail to redirect users who authenticated successfully back to the primary HTTPS port.

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.

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.

Updated 3rd party library

Adapter works with PingFederate authentication policies

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.

Added support for retrieving additional certificate elements and mapping them to attributes.

Added ability to access the certificate chain as J2SE X509Certificate objects via OGNL expressions.

Initial release.