Hey all,
I was originally trying to setup some custom triggers to determine who
should use MFA and who is allowed to bypass. I have since been directed
towards Groovy to simplify things, but I'm still having some trouble.
At this point, the Groovy script's purpose is strictly to test if a
ueves, 8 de febrero de 2018, brian mancuso <snid...@gmail.com
> > escribió:
>
>> Alright Misagh and Manfredo, I believe you're both putting me on the
>> right track with this. Unfortunately, I haven't used a groovy script before
>> and I'm having trouble getting
Alright Misagh and Manfredo, I believe you're both putting me on the right
track with this. Unfortunately, I haven't used a groovy script before and
I'm having trouble getting it to get picked up by CAS. Could either of you
help with this example?
*/etc/cas/selectiveDuo.groovy:*
def String
.@apereo.org
> *Sent: *Tuesday, February 6, 2018 10:56:18 AM
> *Subject: *Re: [cas-user] Multiple Duo Instances
>
> So in my opinion you have a globaltriggerpolicy mfa-duo and eg a groovy
> trigger for employees.
>
>
> https://apereo.github.io/cas/5.2.x/installation/Configuring-
hieved through custom authentication handler?
>
> El martes, 6 de febrero de 2018, brian mancuso <snid...@gmail.com
> > escribió:
>
>> We would like to allow users in a specific ldap group the ability to
>> optionally bypass Duo for a given service if the user is
We would like to allow users in a specific ldap group the ability to
optionally bypass Duo for a given service if the user is not signed up for
a 2fa account. Essentially there would be these two cases for a user:
- 2fa always required
- 2fa optionally required (but always required if the user
