Well, that is disappointing and reassuring at the same time. Thankfully, I am just beginning the process of utilizing interrupts in this way, so I can easily shift my mindset for designing interrupts in the future. Thank you for your quick feedback!!
Shawn On Tuesday, December 4, 2018 at 10:39:17 AM UTC-5, Shawn Cutting wrote: > > Good morning, > I am trying to create a dynamic interrupt page and I think I am > misunderstanding what the "ssoEnabled" setting does. From the > documentation, it seems that if this is set to true, then it would give a > service ticket despite the action that would be taken on the interrupt > page. Here is what I am trying to do: > > I want to warn people that their passwords are about to expire (we use > Active Directory as LDAP) and I am giving them the option to "Remind me in > 3 days." This option updates a database with the reminder date and then > should redirect to the service page they originally called. But instead, > it takes them back to the CAS login where they have to reauthenticate and > it bypasses the interrupt per my code. What I want it to do is, after > pressing "Remind me" to take them to the service page without having to > authenticate again, which is what I thought should happen with > "ssoEnabled=true." > > Can anyone give me some better insight? > Thanks! > -- - 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/2ea85375-af1d-4cd3-8158-b84a56de909d%40apereo.org.
