Hey, 

I'm moving from 5.3.x to 6.2.7 and I'm stymied in my progress by something 
I hope is obvious.  Since it is happening in both 6.2.7 and 6.3.0, I'm 
hoping it is just miss configuration on my part and I'm hoping to get some 
guidance.

Below are the relevant configurations ported from v5.3. Most notably I had 
to convert all these properties from camelCase to hyphenated-lowercase.  
The issue is that, it does not seem to respect the trigger attributes as 
5.3 does.  My assumption is that only folk in a group called 
multifactor-authentication will be prompted for DUO.

If I enable global mfa, by setting the provider id, all requests including 
delegate auth are transitioned to the duo workflow:  They either are asked 
to setup mfa on a phone, or it just fails (delegate without enough info).  
Currently I only have one MFA provider.

# Duo Security
cas.authn.mfa.duo[0].id=mfa-duo
cas.authn.mfa.duo[0].rank=0
cas.authn.mfa.duo[0].name=Duo Security
cas.authn.mfa.duo[0].duo-secret-key=myFirstSupaSekritKey
cas.authn.mfa.duo[0].duo-application-key=mySecondSupaSekritKey
cas.authn.mfa.duo[0].duo-integration-key=myTirdSupaSekritKey
cas.authn.mfa.duo[0].duo-api-host=api-8675309.duosecurity.com

#Global MFA
cas.authn.mfa.request-parameter=authn_method
cas.authn.mfa.global-provider-id=mfa-duo
cas.authn.mfa.global-failure-mode=OPEN
cas.authn.mfa.global-principal-attribute-name-triggers=isMemberOf
cas.authn.mfa.global-principal-attribute-value-regex=.*cn=multifactor-authentication.*

-- 
- 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/c6b01cd3-a927-49a4-a0ff-3bf5d52de24bn%40apereo.org.

Reply via email to