:
>>> cas.authn.mfa.gauth.json.location=file:/etc/cas/mfa.json
>>> But it's the JPA that is problematic.
>>>
>>> cheers,
>>> Jaanus
>>> On Thursday 14 March 2024 at 17:19:04 UTC+2 King, Robert wrote:
>>>
>>>> Those specific
; On Thursday 14 March 2024 at 17:19:04 UTC+2 King, Robert wrote:
>
>> Those specific keys are not included in your application.properties that
>> you originally provided. Only encryption keys in the file are for cas.tgc
>> and cas.webflow.
>>
>>
>>
>&g
t; On Thursday 14 March 2024 at 17:19:04 UTC+2 King, Robert wrote:
>>
>>> Those specific keys are not included in your application.properties that
>>> you originally provided. Only encryption keys in the file are for cas.tgc
>>> and cas.webflow.
>>>
>>
nt:* Thursday, March 14, 2024 11:14 AM
> *To:* CAS Community
> *Cc:* King, Robert
> *Subject:* Re: [EXTERNAL SENDER] [cas-user] Google Authenticator JPA
> account not persisted
>
>
>
> Yes, I do have them defined, as I already learned my lesson back in ver
> 6.5.0 :)
>
] [cas-user] Google Authenticator JPA account not
persisted
Yes, I do have them defined, as I already learned my lesson back in ver 6.5.0 :)
You can see these and other properties in the attachment of my previous post.
So it's not the missing encryption keys this time, but rather some other an
Yes, I do have them defined, as I already learned my lesson back in ver
6.5.0 :)
You can see these and other properties in the attachment of my previous
post.
So it's not the missing encryption keys this time, but rather some other
anomaly
which I cannot figure out.
cheers,
Jaanus
On Thursday
Do you have the following defined in your properties?
cas.authn.mfa.gauth.crypto.encryption.key
cas.authn.mfa.gauth.crypto.signing.key
Maybe not relevant to the missing DB write, but exhibits the same behavior of
MFA not persisting past restart. If you do not define the keys in your
properties
