Cache too old for user about multiotp

[multiOTP]

Hi,
the cache is usually used when multiOTP server is not reachable. Can you tell us what is the scenario ? On what plateforme are you trying to authenticate with multiOTP ?

Best regards.

Hi again,
thanks for reply quick,
our scenario is AWS Workspaces,
the workspaces are authenticated with our Windows Active Directory in AWS.. (not Directory Services of AWS) and the otp is used with multiotp container to secure the autentication to those workspaces.
the rest of users working fine.. it's just this user not used for long time seems to be locked. or cached say that.
is possible clean that user only or have to clean all cached ?
i don't want to recreate again the user, maybe works but have to re-send again the QR to the other admins. I want to try a comand to solved without destroy/delete/re-create actual user.

hi @multiOTP any update to delete the cache without delete it or re-create the user?

[multiOTP]

Hello,
First "emergency" short answer in order to reset the cache flag.
Open the file "myUser.db" on the client side and edit change the value autolock_time=nnnnnnnnnn to autolock_time=0

Now, the long answer:
You are certainly using multiOTP in a client/server configuration.
In a client/server configuration, on the client side, an XML request is initiated to the server during each authentication. If the authentication is successful, local user database on the client side is updated with user information, and the end of life of the cache is set by default to 6 months after the current time. This information is saved in the autolock_time attribute.
When the autolock_time epoch time is older than the current time, the message "Error: cache too old for user myUser, account autolocked" will appear.

It is strange that the XML request to the server has failed for so long tiime. Be sure that theses different points are correct on the client side:

• server_secret is the correct one on both side
• FQDN of the server is the correct one

Thanks to keep us in touch

Best regards

Hi @multiOTP

thanks. it works