Hello All,
I am testing the latest CAS 6.4.0-RC5 build with 2 services
registered with CAS.
Service A: uses Username, Password and MFA (GoogleAuth)
Service B: uses SAML2 with CAS as the IdP
I first sign first into Service A successfully using Username, Password,
Token and then attempt to navigate to the URL for Service B. My expectation
is that CAS will recognize the SSO session that already active and grant
access to Service B. However, CAS seems to redirect me back to the login
screen again. If I authenticate again using the same credentials, then I am
able to access Service B. The same issue occurs in the reverse scenario as
well (Service B first, Service A next).
After examining the logs with Trace turned on, I see a CAS log entry
indicating the Ticket Granting Cookie was blank when trying to access the
second service.
Is there a known issue with SSO sessions/TGC cookies with the RC5 release
or additional config that needs to be completed?
Regards,
--
- 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/ece281f9-ebae-450a-97b3-6eb296451c1cn%40apereo.org.
