Changelog

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.

Initial release