Problem URL with # on login shibboleth
Cantor, Scott
cantor.2 at osu.edu
Wed Jul 29 10:04:05 EDT 2015
On 7/29/15, 9:49 AM, "users on behalf of Teresa Fasano" <users-bounces at shibboleth.net on behalf of t.fasano at cineca.it> wrote:
>Il 29/07/2015 15:37, Peter Schober ha scritto:
>
>Re-reading this you're saying that the SP keeps the "correct" (incl
>the fragment identifier) URI if the browser has an SSO session at the
>IDP, but the URI is missing the fragment identifier if I have to enter
>credentials at the IDP?
>
>Yes, it is.
>If I have to log in
>(enter credentials on the login page),after the authentication the URLbecomes https://<url>without the part relating
>to the character #.
>Instead,if I'm already authenticated,the URL is
>"https: //<url> =# filter ....".
As Peter said, I'm fairly sure that's impossible. If you can supply a web server access log documenting that the web server is actually receiving a URL with a fragment in it, I'll think about it further.
-- Scott
More information about the users
mailing list