...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.
Andy Ng
unread,
Aug 22, 2017, 5:04:41 AM8/22/17
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to CAS Community
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
Andrew Morgan
unread,
Aug 22, 2017, 12:28:09 PM8/22/17
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to CAS Community
Fragments (named anchors) are not sent to the server. Search your web
server access logs - you won't see a "#" in them. :)