Hastags in service URL to CAS

[Waldbieser, Carl]

I believe "#" is a reserved character in a URL.
The part of your URL after the "#" is probably being parsed as a fragment[1].

    https://uuuuu.yy.xx.se/index/#/node/14
    ^^^^^^  ^^^^^^^^^^^^^ ^^^^^^ ^^^^^^^^^
    scheme  authority part path  fragment

So if it is not URL encoded, it won't even be sent to the server.
If it is URL encoded as you show below, the IdP ought to parse something like this:

  'service' = 'https://uuuuu.yy.xx.se/index/#/node/14'
  ^^^          ^^^^^^                       ^^^^^^^^^^
  key          value                        fragment part

So when you are redirected to the service, the fragment part is placed at the end, because that is where it is supposed to go.

Thanks,
Carl Waldbieser
ITS Systems Programmer
Lafayette College


[1] https://en.wikipedia.org/wiki/URL#Syntax

----- Original Message -----
From: "Tobias Galéus" <tobias.galeus at gu.se>
To: users at shibboleth.net
Sent: Tuesday, November 14, 2017 5:11:38 AM
Subject: Hastags in service URL to CAS

Hi!

I'm trying to use CAS to login to a URL which includes a hashtag ( Example:
https://uuuuu.yy.xx.se/index/#/node/14 ), but even if the service is
URL-encoded in the request to Shibboleth:
https://idp.ourdomain.se/idp/profile/cas/login?service=https%3a%2f%2fuuuuu.yy.xx.se%2findex%2f%23%2Fnode%2F14

the user ends up on
https://uuuuu.xx.yy.se/index/?ticket=ST-1510123581962-OoDx1hFAf0pb0FJX2MgSpsvtP#/node/root
instead of
https://uuuuu.xx.yy.se/index/#/node/root?ticket=ST-1510123581962-OoDx1hFFW0pw0IJX2MhSppvtP

Am I doing something wrong? Is it a bug? What is the correct way to solve
this?

We're using Shibboleth 3.3.1 and 3.3.2 which both shows the same result.

Best regards,
Tobias



--
Sent from: http://shibboleth.1660669.n2.nabble.com/Shibboleth-Users-f1660767.html
-- 
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