Hi,
The behaviour you describe used to be possible in old CAS, but it's not
possible anymore.
The question is: why you need this?
And IMHO you should not encode the hash param. ie, you should use login url:
https://10.20.30.40/login?service=https%3A%2F%2F10.20.30.40%2F#/app-dashboard/
The "#/app-dashboard/" part will be added through 302 redirects.
And should even be kept on password login FORM (thanks to
"preserveAnchorTagOnForm" js)
cu
On 28/10/2022 09:25, Priyanka Choudhary wrote:
Hi,
I have service id as:
"serviceId" : "^(https|imaps|http)://.*/#/app-dashboard/",
and I am using url for login as
https://10.20.30.40/login?service=https%3A%2F%2F10.20.30.40%2F%23%2Fapp-dashboard%2F
and 302 redirect I see as
https://10.20.30.40/?redirect=true&tikect=xxxxxxygg#/app-dashboard/
But it should be
https://10.20.30.40/#/app-dashboard/?redirect=true&tikect=xxxxxxygg.
Please let me know how to fix it.
Thank you.
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are subscribed to the Google Groups "CAS Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/a/apereo.org/d/msgid/cas-user/11101481-0358-d290-fe25-158e4043af11%40univ-paris1.fr.
