Previously configured and have been running CAS 6.6 in production for a
while.
Recently looking to upgrade to CAS 7.0.
Able to build and run 7.0, but it will only listen on 127.0.0.1 regardless
of all efforts otherwise.
have tried the following with cas.properties,
server.address=x.x.x.x
We are using simple MFA, but as far as the expiration (need to re-MFA) goes
the following may help.
Researched every possible expiration property and found they were ignored.
If you take a close look at the "expirationDate":
"2123-11-03T09:23:27.000+00:00" from your note, this is set to
Our model cas 6.6.6 is not exactly as yours (ours is DBMS/Azure rather than
LDAP) but likely parallels the issue so may provide some perspective.
Authentication model where some users authenticated with DBMS name/pass and
others through Azure. Challenge was how to make the released
hich is what we use,
>>>
>>>
>>> On Tuesday, July 25, 2023 at 3:41:02 PM UTC-5 Ray Bon wrote:
>>>
>>>> Anthony,
>>>>
>>>> Does surrogate+username / password approach work, or is it only the
>>>> surrogate selectio
rvice that requires MFA, it goes through the
>> mfa flow for username and then to service as surrogate. But I do not have
>> any groovy scripts running.
>>
>> Ray
>>
>> On Tue, 2023-07-25 at 10:31 -0700, Anthony Oslund wrote:
>>
>> Notice: This message was
CAS 6.6.6
Have Simple MFA expiration working in production with couchDb, but had
noticed an issue.
No matter how configured, the expiration of the MFA couchDb record is
always written at 100 years from record creation date.
Only work around I could find for this was to add a "by_not_processed
Start by stating current deployment uses 6.6.6 with DBMS authentication,
not LDAP.
Deployment uses the groovy approach for triggering simple MFA.
Based on much testing and researching of this archive determined that if
simple MFA is activated through groovy script that CAS will bypass
CAS 6.6.6
Is it possible to use Simple MFA as part of initial authentication and then
flow to Surrogate selection?
(1) Have full deployment working with MFA, and Surrogate functioning, but
not for the same authentication instance. If MFA triggered during
authentication then surrogate
