Hi again... Debugging the default CAS login flow when an AuthenticationHandler throws an Exception (i.e. UnauthorizedSsoServiceException) I see that the PolicyBasedAuthenticationManager handles that exception adding it to the failures list and finally throws an AuthenticationException. It seems to be fine.
But when that AuthenticationException is handled by the login web flow, the FlowExecutionExceptionHandlerSet has the following exceptions: > class > org.apereo.cas.services.UnauthorizedServiceForPrincipalException=serviceUnauthorizedCheck, > class > org.apereo.cas.services.UnauthorizedServiceException=serviceUnauthorizedCheck, > class > org.apereo.cas.services.UnauthorizedSsoServiceException=viewLoginForm, > class > org.springframework.webflow.execution.repository.NoSuchFlowExecutionException=viewServiceErrorView Even when the thrown exception was one of that set, the login web flow is not able to identify that transition (it receives an AuthenticationException). This is a weird behaviour, isn't it? Is there any easy way to extend the login web flow to add the org.apereo.cas.authentication.AuthenticationException to the exceptionHandlers set? -- - 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 cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/db175d8a-6620-4145-aa38-d0c1c365e778%40apereo.org.
