change of response URL

Rohit Shinde rohit at
Sun Nov 18 01:14:30 EST 2018

Can you please help me to get rid of 302 error for mydomain/Shibboleth.sso/SAML2/POST

> On 18-Nov-2018, at 10:59 AM, Rohit Shinde <rohit at> wrote:
> When I changed homeURL to https://mydomain/saml/consume <https://mydomain/saml/consume> its redirecting to new home page instead of https://mydomain <https://mydomain/> but I was expecting SAMLResponse from idp on new homeURL. 
>> On 18-Nov-2018, at 10:34 AM, Nate Klingenstein <ndk at <mailto:ndk at>> wrote:
>> Rohit,
>>> 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 <https://mydomain/Shibboleth.sso/SAML2/POST>  where SAMLResponse is and after that its getting redirected to https://mydomain <https://mydomain/>
>>> How to get rid of 302 error?  
>> The 302 probably isn't an error.  That's the way the software redirects you to the protected resource after it's finished consuming an assertion and creating a session using it.  It's redirecting you to the base URL because it doesn't have a functional place to send you(e.g. no relay state in the SAML Response).  You can set a different default(homeURL on the Sessions element) if for some reason your deployment environment can't set a proper destination URL.
>> I'd turn up the SP's logging to DEBUG and look at /var/log/shibboleth/shibd.log, where you should see a session being created.
>> Thanks,
>> Nate.
>> -- 
>> For Consortium Member technical support, see <>
>> To unsubscribe from this list send an email to users-unsubscribe at <mailto:users-unsubscribe at>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the users mailing list