User1628690435355562927 (Customer) asked a question.
Non-Standard SAML Implementation, Custom Post Parameters
We have a third-party vendor which leverages a non-standard implementation of SAML authentication.
Normally, Okta (as is industry standard) sends a POST request to the SAML Assertion Consumer Service (ACS) URL, structured as follows:
POST Payload Format:
- application/x-www-form-urlencoded
POST Payload Parameters:
- SAMLResponse=[SAML RESPONSE BASE64 GOES HERE]
This vendor, however, requires a POST request structured as follows:
POST Payload Format:
- application/x-www-form-urlencoded
POST Payload Parameters:
- ssoMethod=SAML2
- target=jsp/portal/portal.jsp
- ssoToken=[SAML RESPONSE BASE64 GOES HERE]
Does Okta support customization of a SAML app on that level? Is there a way to customize the SAML response payload sent to the application (the actual post request, not the data within the SAML response).
Hi @User1628690435355562927 (Customer),
I let others chime in as well, but I would be surprised if there's a way since you're talking about non-standard SAML assertion.
-Jani
Hi, @User1628690435355562927 (Customer)
Thank you for posting on our Okta community page!
I did some extensive research on the subject and this article gives input on non-standard SAML application implementation:
You can also try to take a look at SAML assertion inline hooks:
Hope this helps!
Thank you for reaching out to our Community and have a great day!
_____________________________________________________________________________
The Okta Community Catalysts Program is now live. Collect online badges when you participate in the Okta Help Center Questions community. Learn more here.
_____________________________________________________________________________