RelayState/Deeplink not working
search cancel

RelayState/Deeplink not working


Article ID: 6188


Updated On:


CA Single Sign On Secure Proxy Server (SiteMinder) CA Single Sign On SOA Security Manager (SiteMinder) CA Single Sign-On


Although a RelayState (deeplink) value was included in the SP-initiated federation request, the user was brought to the default Target page for the SP application rather than the expected RelayState URL.


All current releases of Siteminder


This problem can have multiple causes.   

First, if the SP software is Siteminder, there is an option to allow the RelayState to override the Target.  By default this option is not selected.   

Second, the RelayState parameter name is case sensitive, and thus must appear just as it does in this document.  


Assure that the SP software is configured to honor any RelayState values, and make sure the case is correct within the RelayState parameter name itself.