We are using 5.2.0 and we applied mentioned above changes to TerminateSessionAction.java <https://github.com/apereo/cas/blob/master/support/cas-server-support-actions/src/main/java/org/apereo/cas/web/flow/logout/TerminateSessionAction.java> . But it doesn't help in a situation when user stays to long on CAS login page and web session gets timed out. In that case pac4JRequestedUrl gets lost with the session and user after login will be redirected to /. So we ended up changing both DefaultSecurityLogic and DefaultCallbackLogic to save pac4JRequestedUrl in cookies besides saving it to session.
On Tuesday, January 29, 2019 at 6:42:44 PM UTC+6, Geoff wrote: > > I ran into this in 5.1.x and fixed it by modifying > TerminateSessionAction.java to preserve the pac4JRequestedUrl when killing > the session. > > I found this fix in a newer version of TerminateSessionAction, I thought > it was made prior to 5.2.5 but maybe not. > > > https://github.com/apereo/cas/blob/master/support/cas-server-support-actions/src/main/java/org/apereo/cas/web/flow/logout/TerminateSessionAction.java > > > > On Jan 28, 2019, at 9:45 PM, Abylay <[email protected] <javascript:>> > wrote: > > Hi, does anyone have solution for this? > > On Monday, July 2, 2018 at 5:38:25 PM UTC+6, Diego Henrique Pagani wrote: >> >> Hi everyone, >> >> >> i'm having an issue. I have some application that delegates >> authentication to CAS 5.2.5 using OAuth2.0 protocol. When someone not >> authenticated access the application, the application redirects to CAS. If >> the person do not authenticate after some time (or delete the cookies) and >> submit the form, CAS authenticate the person but, instead of redirect to >> the service mentioned in the URL param, it redirects to "/". >> >> After some debbugging, I found out that the class >> "DefaultCallbackLogin.java", the method "redirectToOriginallyRequestedUrl" >> does the job to redirect, but, it get's from the Session, not from the URL, >> so, erasing the cookies or have them invalid, lost the redirect. >> >> Does someone know how to solve that issue? Because some users are getting >> lost, causing an increase number of ticket relating this issue. >> >> 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] <javascript:>. > To view this discussion on the web visit > https://groups.google.com/a/apereo.org/d/msgid/cas-user/317a9de0-e82d-4829-9912-087bfd16efd8%40apereo.org > > <https://groups.google.com/a/apereo.org/d/msgid/cas-user/317a9de0-e82d-4829-9912-087bfd16efd8%40apereo.org?utm_medium=email&utm_source=footer> > . > > -- - 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/51c807f1-334d-4e7e-8126-5f62b4f2cfe8%40apereo.org.
