Closed dima767 closed 9 years ago
Most likely, this is caused by cas-addons 16 which brings in a bunch of new JARs. MFA uses 13. I'll see if I can update the pom.
This is now done.
Can we reopen this? I'm seeing the same problem.
It seems to be caused when the json service registry is enabled. The value of the mfa.default.authn.method
property is ignored as far as I can tell. If authn_method
isn't set by the service registry then the value is assumed empty and you get the NoSuchMethodError exception. Setting it explicitly to an empty value results in the same. The only thing that works is to set it to a valid value from auth-methods.conf. In my case this would duo-two-factor
.
The end result of this is that there is no way to have a service with MFA disabled.
What you're describing sounds different than the bug above, which had to do with dependency issues. Please open up a separate issue and we'll investigate.
Also, please specify whether you are running from source, or whether you have integrated this into your overlay, and if so, please attach a pom as well as the snapshot of the error stack trace you see.
CAS version:
3.5.3
cas-mfa version:
1.0.0-RC1
pom.xml:
Runtime exception thrown: