We are trying to upgrade from CAS 5.1.3 to 5.3.7 to get per-service JWT encryption & signing keys. I believe I ported all of our customized code to the new versions of the files & classes in question:
- CasCoreWebflowConfiguration - add 3 handled exceptions - DefaultLoginWebflowConfigurer - additional action states for non-standard login flow - DefaultLogoutWebflowConfigurer - redirect to our version of casFrontChannelLogoutAction - InitializeLoginAction - add in CSRF token; pass in some configuration values into the flow scope - LogoutAction - URLDecode the service param; handle our session synch cookie. - AbstractServiceValidateController - expose attributes for use in service validation web page - login-webflow.xml - insert CSRF token validation; add 'change your password' flow; Currently, I'm seeing that org.apereo.cas.web.flow.resolver.impl.AbstractCasWebflowEventResolver.grantTicketGrantingTicketToAuthenticationResult() is no longer creating the TGT that sendTicketGrantingTicketAction will later pack up into the TGC during login-webflow. Blindly, I tried inserting createTicketGrantingTicketAction in the flow, but of course that didn't work. Can someone point me to where CAS now expects to be creating the TGT? -- - 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/fb24568f-41fd-4e68-866b-cd0502b96a60%40apereo.org.
