Form Based SSO for Dynamically built HTTP forms
Problem this snippet solves: This snippet solves a challenge where Client Initiated Form Based SSO is required but you have no available trigger that you can configure to allow APM to detect the for...
Published Oct 16, 2018
Version 1.0Yann_Desmarest
Cirrus
Joined September 11, 2012
Yann_Desmarest
Cirrus
Joined September 11, 2012
Nov 14, 2018
Hi Yann, thanks for updating. I stumbled into another error. An user was using the ampersand character in the password. The solution in this case was to use
URI::encode
the password. The client was already sending the Content-Type: application/x-www-form-urlencoded
header, so there was no need to add this header. See the changes in the HTTP_REQUEST_DATA event below.
set password [URI::encode [ACCESS::session data get -secure session.sso.token.last.password]]
set newpayload [string map [list "f5-sso-token" $password] $payload]