change of response URL

Rohit Shinde rohit at venturit.com
Sat Nov 17 23:58:24 EST 2018


This change of response came in my mind because currently I am getting response in mydomain/Shibboleth.sso/SAML2/POST but the problem is I am getting 302 error for https://mydomain/Shibboleth.sso/SAML2/POST  where SAMLResponse is and after that its getting redirected to https://mydomain
How to get rid of 302 error?  

> On 18-Nov-2018, at 10:02 AM, Nate Klingenstein <ndk at signet.id> wrote:
> 
> Rohit,
> 
>> After change URL appears to be mydomain/Shibboleth.sso/saml/consume but I would prefer to be  mydomain/saml/consume
> 
> You could accomplish this by renaming the handlerURL in the Sessions element to "saml" instead of the default "Shibboleth.sso":
> 
> https://wiki.shibboleth.net/confluence/display/SP3/Sessions
> 
> and using the long-form configuration to explicitly locate the SAML POST consumer endpoint at "consume":
> 
> https://wiki.shibboleth.net/confluence/display/SP3/SAML2+Sessions+Configurations
> 
> which will create a combination of mydomain/saml/consume.
> 
> Note that this will change the location and functionality of a variety of other pieces of the software; the session handler would be at mydomain/saml/Session, for example, and if you only listed the POST assertion consumer service, you would lose support for other session creation methods.
> 
> Also, you'll need to make sure your configuration and your metadata match precisely; changing just one or the other alone will break things.
> 
> I personally wouldn't bother doing all that just for cosmetic purposes, but it's certainly possible.
> 
> Hope this helps,
> Nate.
> -- 
> For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net



More information about the users mailing list