Re: [cas-user] CAS 5.2.3 "500:Internal Server Error" with Groovy

> you should get > > 2018-02-09 19:10:39,145 DEBUG > [org.apereo.cas.authentication.GroovyMultifactorAuthenticationProviderBypass] > - [casuser], service [null] and provider > [DefaultDuoMultifactorAuthenticationProvider] via Groovy script [URL > [file:/etc/cas/config/mfaGroovyTrigger.groovy]]>

Re: [cas-user] CAS 5.2.3 "500:Internal Server Error" with Groovy

uthenticationProvider] via Groovy script [URL > [file:/etc/cas/config/mfaGroovyTrigger.groovy]]> > > > > > > 2018-02-09 17:11 GMT-03:00 Brian Davidson <mailto:awk.br...@gmail.com>>: > Just to add a bit to what Brian M. provided (I’m also a Brian, and

Re: [cas-user] CAS 5.2.3 "500:Internal Server Error" with Groovy

.2 > > El sábado, 10 de febrero de 2018, Brian Davidson <mailto:awk.br...@gmail.com>> escribió: > I meant to add, our pom.xml has the following dependencies (in case we’re > missing something): > > > > org.apereo.cas >

Re: [cas-user] CAS 5.2.3 "500:Internal Server Error" with Groovy

> > > El sábado, 10 de febrero de 2018, Brian Davidson <mailto:awk.br...@gmail.com>> escribió: > Running on apache-tomcat-8.5.24, so that should be servlet v3.1.x. > > Yes, this is CAS version 5.2.2. > > CAS w/ Duo works with no bypass groovy script in place.

Re: [cas-user] CAS 5.2.3 "500:Internal Server Error" with Groovy

...@gmail.com>> wrote: >> >> Why you hace this >> >> >> >> javax.servlet >> servlet-api >> 2.5 >> jar >> >> >> >> El sábado, 10 de febrero de 2018, Brian Davidson >

Re: [cas-user] CAS 5.2.3 "500:Internal Server Error" with Groovy

(GroovyMultifactorAuthenticationProviderBypass.java:40) ~[cas-server-core-authentication-mfa-5.2.2-SNAPSHOT.jar:5.2.2-SNAPSHOT] … > On Feb 10, 2018, at 10:14 AM, Man H wrote: > > Try returning string "mfa-duo" or null > > El sábado, 10 de febrero de 2018, Brian Davidson <mailto:awk.br...@gmail.co

Re: [cas-user] CAS 5.2.3 "500:Internal Server Error" with Groovy

If it completes successfully and then you again enable groovy > bypass and then after it you get the failures that you are seeing, then the > problem indeed is somewhere in that bypass facility. > > Cheers, > D. > > > > > On Sat, Feb 10, 2018 at 11:29 AM -0500, "Br

Re: [cas-user] CAS 5.2.3 "500:Internal Server Error" with Groovy

Man, Just providing clarification on this other issue that I hadn’t gotten back to you on. I think the issue in this specific email is an issue with duo.com , while the other issue in this thread is an issue with CAS. In order for CAS to be able to use Duo you must obtain an i

Re: [cas-user] CAS 5.2.3 "500:Internal Server Error" with Groovy

e. > > D. > > > > > On Sat, Feb 10, 2018 at 12:01 PM -0500, "Brian Davidson" <mailto:awk.br...@gmail.com>> wrote: > > I have tried that. Duo works when I disable the bypass facility. When I > enable it, if bypass script returns false, single factor

Re: [cas-user] CAS 5.2.3 "500:Internal Server Error" with Groovy

t 7:34 AM, Brian Davidson wrote: > > Man, > > Just providing clarification on this other issue that I hadn’t gotten back to > you on. I think the issue in this specific email is an issue with duo.com > <http://duo.com/>, while the other issue in this thread is an issue w

Re: [cas-user] CAS 5.2.3 "500:Internal Server Error" with Groovy

;> escribió: > Thanks for confirming. Sounds like a bug to me. > > D. > > > > > On Sat, Feb 10, 2018 at 12:01 PM -0500, "Brian Davidson" <mailto:awk.br...@gmail.com>> wrote: > > I have tried that. Duo works when I disable the bypass faci

Re: [cas-user] CAS 5.2.3 "500:Internal Server Error" with Groovy

Just to add a bit to what Brian M. provided (I’m also a Brian, and a co-worker of Brian M’s): We have Duo MFA working if we comment out: cas.authn.mfa.duo[0].bypass.type=GROOVY cas.authn.mfa.duo[0].bypass.groovy.location=file:///etc/cas/selectiveDuo.groovy We did find that CAS was unable to ch