Changelog

The following is the change history for the PingAM Integration Kit.

PingAM Integration Kit 1.2 - February 2025

Added the ability to use backchannel communication with PingAM to pass data from PingFederate to PingAM securely.

To send PingFederate parameters to PingAM, you must create an OAuth client in PingAM and update the PingAM IdP Adapter configuration with the associated Client ID and Client Secret.

Learn more in step 6 of Preparing to use a PingAM journey and refer to the Client ID and Client Secret table entries in PingAM IdP Adapter settings reference.
Added the ability to configure whether the PingAM session should be deleted after a user signs off from the protected application.

Learn more in the Logout Mode table entry in the PingAM IdP Adapter settings reference.

Added the ability to track PingFederate and PingAM transactions using a unique request ID that’s set by the adapter. This enhances the application log debugging experience. You can find configuration instructions in Tracking transactions between PingFederate and PingAM.
Added the ability to perform username validation. To do so, configure the Username Path between the username that the adapter receives from the authentication policy and a value in the PingAM session info payload.
Fixed an issue that caused an infinite loop between PingFederate and PingAM if the PingAM and adapter cookie name values didn’t match. The adapter now fails if it doesn’t receive the expected cookie name from PingAM.