I am not using the name anchor in my use case, but after some testing: I think that saving the named anchor is not a feature that is implemented for all login methods for CAS. For example, in my website: normal login (username & password) will preserve the name anchor (I have checked that both Firefox and Chrome works), while using pac4j delegated login will completely drop my named anchor.
Don't know whether there is an setting in cas properties that will enable saving the name anchor, I doubt it. If I were you I might try just using some javascript tricks to save the anchor value to an localStorage or something before login, and resume it to the user when they land the login page for the second time. -Andy On Monday, 21 August 2017 21:33:15 UTC+8, Dusty Edenfield wrote: > > Is there any solution for when CAS drops named anchors upon login redirect? > > Example: > It appears (from LiveHTTPHeaders and HTTPFox traces) that CAS is dropping > named anchors from target URLs. For example, going to the CAS-protected URL: > > https://somesite.edu/reports/#Mobile > > results, after authentication, the browser ending up at: > > https://somesite.edu/reports/ > > ...sans the named link reference. This is a problem in multiple browsers, > and I don't know if this is a bug in CAS, or a bug in our implementation of > CAS. > > > -- - CAS gitter chatroom: https://gitter.im/apereo/cas - CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html - CAS documentation website: https://apereo.github.io/cas - CAS project website: https://github.com/apereo/cas --- 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 cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/2c3611a7-9adb-47de-ade8-eb868f2c02eb%40apereo.org.
