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

lt;dkopyle...@unicon.net > <mailto:dkopyle...@unicon.net>> escribió: > Thanks for confirming. Sounds like a bug to me. > > D. > > > > > On Sat, Feb 10, 2018 at 12:01 PM -0500, "Brian Davidson" <awk.br...@gmail.com > <mailto:awk.br...@gmail.com

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

t 7:34 AM, Brian Davidson <awk.br...@gmail.com> 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 is

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

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

ion > transaction. 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 1

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 <info.ings...@gmail.com> wrote: > > Try returning string "mfa-duo" or null > > El sábado, 10 de febrero de 2018, Bria

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

s}") > > return true > } > > > El sábado, 10 de febrero de 2018, Brian Davidson <awk.br...@gmail.com > <mailto:awk.br...@gmail.com>> escribió: > Removed that dependency and still git the same 500 error and same stack trace. > >> On Feb 10, 2018,

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

jar > > > > El sábado, 10 de febrero de 2018, Brian Davidson <awk.br...@gmail.com > <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.

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

ovider > [DefaultDuoMultifactorAuthenticationProvider] via Groovy script [URL > [file:/etc/cas/config/mfaGroovyTrigger.groovy]]> > > > > > > 2018-02-09 17:11 GMT-03:00 Brian Davidson <awk.br...@gmail.com > <mailto:awk.br...@gmail.com>>: > Just to add a

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/confi

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