@MariusHechter11599 (Customer)​ ,

Some things for you to check:

• What agent is your RSAUSER2 using for authentication (Windows, PAM)? Note that the RSA Authentication Agent 7.4.x for Windows and the RSA Authentication Agent 8.1.x for PAM are no longer supported. If you are using and of the UDP-based agents, please upgrade to a supported MFA agent and test again.
• What version of the agent?
• Is this happening for more than one user?
• Is the RSAUSER2 locked? Search for the user in the Security Console and unlock their account if locked.
• Are you testing with hardware tokens or software tokens?
• If you are using a software token, has the token been redistributed or reissued? If so, the old tokens become invalid, and users must import the new token data.
• If you are using the older agents, ensure that the IP address for the agent machine matches the IP address listed on the agent record in the Security Console.
• Is replication healthy between your servers?
• Can you authenticate with a fixed passcode? If so, this indicates a time issue between the token and the servers.
• System resource constraints or database errors can cause authentication failures. Check system memory, CPU, and database health.
• Ensure there is sufficient storage and that the database is operating correctly. SSH to the primary and run both df -h and df -i to look at the Use percentage for /dev/sda3.