Changelog

Verified that the CoreBlox IdP Adapter is compliant with US Federal Information Processing Standards (FIPS). Learn more about usage in Integrating with Bouncy Castle FIPS provider in the PingFederate documentation.

Updated internal components to better support certificate revocation checks in PingFederate 11 and later.

Fixed an issue that could cause a query string to be encoded incorrectly.

Fixed an issue that could rarely cause a redirect loop.

Added the Session Cookie Prefix and Remove Session Cookie Prefix settings to accommodate a change in the way the CoreBlox Token Service provides tokens.

Resolved an error that occurred when a user left the sign on page, then tried to open the sign on page again elsewhere.

Improved PingFederate node reliability when making REST calls to the the CoreBlox Token Service by changing to a bundled HTTP client.

Added an option to ignore session cookies from inbound requests to the PingFederate SP server. Refer to Ignore Session Cookie on the CoreBlox SP Adapter Instance Configuration screen.

Added 'Send Session Attributes' field to SP adapter to send attribute contract to the the CoreBlox Token Service (CTS) to include in the created session.

PingFederate 8.4 compatibility updates

Optionally prevent an update to the session cookie upon log in

User is redirected for authentication if session is invalid

Session cookie is retained and set to the logged off value after SLO

Session cookie isn’t modified on SLO error

Login URL field is made optional to support multiple CoreBlox environments

Improved error logging in both IdP and SP adapters.

Added cookie provider functionality

Authentication Context support added for the SP Adapter scenario

Added the capability in the CoreBlox SP adapter to download a configuration file for the OpenToken agent.

Bug fixes.

Added additional configuration UI validation, notably for the added fields required for authorization and for the "Cookie Domain" in the SP adapter.

Fixed Account Linking. Previously was attempting to use a 'userId-qualifier' as the attribute to link accounts. Now it’s set up to use the 'userId' attribute.

The authentication context for the adapter is now functional. Anything that is entered in the field will appear in the SAML assertion.

Both IdP and SP adapters can be configured to authorize a user before redirecting them to the target resource.

The 'token' attribute returned in the JSON object from the CTS can now be added to the extended contract using the keyword 'token'.

Added authorization functionality, enabling users’ authorization level to be scrutinized before accessing a protected resource.

CoreBlox Integration kit’s debut.