User1707744580167166363 (Customer) asked a question.
URL parameters are dropped when using SAML
Hi,
I created a SAML application in OKTA in order to login to an application we have.
OKTA is the IDP and F5 is the SP.
When I access the login page of my app I sometimes use parameters in the URL, for example:
https://myapp.test.com/page?parameter=value
I noticed the during the SAML negotiation these parameters are dropped.
Is there a way to tell OKTA to keep them?
I also have ADFS configured as IDP for that app and I don't see such behavior there.
L
Thanks
Hello @User1707744580167166363 (Customer) Thank you for reacting out to our Community!
Have you tried to send these parameters as Custom Attributes in the SAML assertion?
To setup custom attributes in the application please see:
https://support.okta.com/help/s/article/How-to-define-and-configure-a-custom-SAML-attribute-statement?language=en_US
Or if you want to define a RelayState please see doc below:
https://support.okta.com/help/s/article/How-to-send-a-custom-relaystate-to-application-through-idp-initiated-authentication-urls?language=en_US
Community members help others by clicking Like or Select as Best on responses. Try it today.
Earn Today: New Okta Community Badges Have Arrived
Ask the experts about Okta Privileged Access
Hi Paul,
Custom Attributes are derived from static data in user profile whereas what I'm talking about are dynamic URL parameters which change each time.
Just to understand - the scenario I described in the question is how it's supposed to behave?
Hello @User1707744580167166363 (Customer) I have looked a bit into this and it seems this is no currently supported, this is mentioned here :
https://devforum.okta.com/t/is-it-possible-to-tack-on-parameters-to-the-redirect-uri/13518
Community members help others by clicking Like or Select as Best on responses. Try it today.
Earn Today: New Okta Community Badges Have Arrived
Ask the experts about Okta Privileged Access