Hmm... interesting, don't know why it doesn't work... For your question about JSESSIONID, CAS mostly do not relies on JSESSIONID to check if user login-ed or not.
Instead, CAS will generate a cookie called *TGC *cookie, and look at this instead. About the login problem, can you *enable debug logs* ( https://apereo.github.io/cas/5.3.x/installation/Troubleshooting-Guide.html#review-logs) and show the log to this group (of course need to hide the sensitive information), because it is hard to debug without more information. Cheers! - Andy -- - 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/e70edc50-8f4a-4cc5-a0b5-5a7e10c11c14%40apereo.org.
