Shibboleth Idp does not persist URL hash fragments across a login redirect.

[Waldbieser, Carl]

I think the point is just that the OP wants the user to wind back up at the full URL (including the fragment) after authenticating.
Could something like the "target" parameter [1] be used at the SP to force the redirect after authentication to end up at a complete URL?

Thanks,
Carl Waldbieser
ITS Identity Management
Lafayette College

[1] https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPSessionCreationParameters

----- Original Message -----
From: "Peter Schober" <peter.schober at univie.ac.at>
To: users at shibboleth.net
Sent: Tuesday, April 12, 2016 11:00:53 AM
Subject: Re: Shibboleth Idp does not persist URL hash fragments across a login redirect.

* Rainer Hoerbe <rainer at hoerbe.at> [2016-04-12 16:06]:
> Shouldn’t the SP store the full URL including the fragment part in the relaystate cookie?

Look at the server logs, the HTTP User Agent never transmits the
fragment identifier, as I said before in the Wikipedia example.
-peter
-- 
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net