Matt, It depends. If during CAS ticket validation, the validation result can assert that MFA took place for the authentication that created the TGT, then I think that would be sufficient if your requirement is simply that MFA took place already in the SSO session.
However, suppose not all services require MFA. If you first establish an SSO session to such a service, you might not be prompted for MFA. When you next go to a service that requires MFA, CAS would need to check in with the IdP so it could perform MFA, or else the SSO session would be denied access until it was terminated and a new SSO session was started that actually did use MFA. If your setup is such that in order to establish an SSO session, you need to have provided a 2nd factor, then I would agree that CAS shouldn't need to check with the IdP each time whether MFA is valid-- the fact that the SSO session exists at all is based on the fact that MFA was successful. Whether it is possible to configure the software that way, I'm not sure. Our own setup is the opposite of yours. We run both CAS and Shibboleth services. CAS clients interface directly with our CAS service. SAML2 clients interact with our Shibboleth IdP, but the IdP delegates all authentication to CAS so the SSO experience is unified. Our CAS service does need to signal to the IdP if MFA was used to establish the session. We require MFA on a per-user basis. Either a user will be required to use MFA to establish an SSO session or it will not. Any call to our IdP will always pass though to CAS to verify an SSO session exists. Users are only prompted for MFA once per session. Thanks, Carl Waldbieser ITS Identity Management Lafayette College ----- Original Message ----- From: "Matt T" <j.matt.thomp...@gmail.com> To: "cas-user" <cas-user@apereo.org> Sent: Friday, 7 September, 2018 09:54:07 Subject: [cas-user] Should the CAS ticket be authoritative? Hi Everyone, I'll be the first to admin I'm no CAS expert. In fact, I don't even manage our deployments here. Instead, I work with applications which interface with it so I do understand to some degree. That being said, I have a question which came up in internal discussions I'm hoping to get some input on. We have CAS delegating authentication to our IDP. Our IDP enforces two-factor auth so if we require it, we don't have to facilitate with CAS. We've run into an issue where every request to an application behind two-factor prompts the user for the second factor of authentication. This happens even when in a browser you've already verified. This is an issue because it takes away from the true SSO experience and a user can't move from app to app. The main reason it is asking for the second factor again is due to the way we integrate CAS into our IDP. That's a whole different topic and really outside of the scope of this questions so just know we're aware of why it happens even if it isn't right. The question is this. Is CAS ticket validity secure enough to trust only that? Why should we even check with our IDP a second time if the user's session already has a valid CAS ticket? Do others use this configuration or do you always check with the IDP? It seems like trusting the CAS ticket if valid is the best option and would allow us to better control application logins and state but maybe I'm not thinking it all the way through. Thanks in advance for any insight! -Matt -- - 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/7ed4ac9e-139b-4273-b491-16ae953a9347%40apereo.org. -- - 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/1982198971.87822549.1536332145477.JavaMail.zimbra%40lafayette.edu.
