Recently during my research i came across the following code from apereo redis ticket repository library . https://github.com/apereo/cas/blob/master/support/cas-server-support-redis-ticket-registry/src/main/java/org/apereo/cas/ticket/registry/RedisTicketRegistry.java#L81
The implication of this code is that we dont throw any exception related RedisConnectionFailureException if the connection between redis cluster and cas is broken . https://github.com/apereo/cas/blob/master/support/cas-server-support-redis-ticket-registry/src/main/java/org/apereo/cas/ticket/registry/RedisTicketRegistry.java#L70 This results in following behaviour . 1. Any Single sign in sessions cant be used any more 2. New users can't log in and will be stuck in login page with out any error message . I have following concerns on the same . 1. Can any one help me understand why we designed the API to eat up the RedisConnectionFailureException . 2. Can we better handle issue #2. -- - 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/55b0bcc1-fd95-4aa2-92b0-8889c0d00fe1n%40apereo.org.
