Baron, I am planning to change the shib-cas plugin to use delegated SAML authn (shib delegating to cas) to solve this problem. Right now if a shib service requires MFA, the user will have to duo in both cas and shib.
Ray On Tue, 2022-07-05 at 10:11 -1000, Baron Fujimoto wrote: Notice: This message was sent from outside the University of Victoria email system. Please be cautious with links and sensitive information. Are the set of CAS authentication attributes documented somewhere? If you test logins using /cas/login, we can see, for example, the following set of authentication attributes: credentialType, clientIpAddress, samlAuthenticationStatementAuthMethod, authenticationDate, bypassMultifactorAuthentication, authenticationMethod, authnContextClass, successfulAuthenticationHandlers, serverIpAddress, userAgent Some of them are straightforward, such as clientIpAddress, authenticationDate, serverIpAddress, userAgent; but it would be helpful to have some formal documentation on exactly what the others are. For example, suppose a client wanted to verify that MFA was actually used. If we only supported Duo for MFA, is it sufficient to simply check, say, successfulAuthenticationHandlers for the value "DuoSecurityAuthenticationHandler", or do you also have to verify bypassMultifactorAuthentication = "false"? Or is there another "correct'' way to do this? Bonus: we also use the shib-cas plugin to front our Shibboleth IdP deployment with CAS. Any pointers to how we can make use of these authentication attributes to define comparable attributes on the Shib side would be appreciated. -- Baron Fujimoto <ba...@hawaii.edu<mailto:ba...@hawaii.edu>> ::: UH Information Technology Services minutas cantorum, minutas balorum, minutas carboratum descendus pantorum -- Ray Bon Programmer Analyst Development Services, University Systems 2507218831 | CLE 019 | r...@uvic.ca<mailto:r...@uvic.ca> I acknowledge and respect the lək̓ʷəŋən peoples on whose traditional territory the university stands, and the Songhees, Esquimalt and WSÁNEĆ peoples whose historical relationships with the land continue to this day. -- - 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/8111d119e970cc251a7998aeccea3de7bec0ce65.camel%40uvic.ca.