Invalid tokencode failures and expired QR code alerts in RSA SecurID Authenticate app
Originally Published: 2019-10-15
Article Number
Applies To
RSA Product/Service Type: Cloud
RSA Version/Condition: Not Applicable
Issue
An end user is encountering one or both of the following problems with the RSA SecurID Authenticate app:
-
Step-up authentications using the RSA SecurID Authenticate app tokencode are failing and the User Event Monitor displays the following error for the attempts
Authenticate Tokencode authentication failed - Invalid tokencode
The above error occurs even when the user is very sure they are entering the correct code displayed on their device.
-
RSA SecurID Authenticate app device registration using a QR code fails. The app displays the following alert:
Expired QR Code. Message: Generate a new QR Code. Then scan the new code in the app .
The user is able to complete registration with a password or registration code however.
Cause
Resolution
For example, if the end user's device region is currently set to India (GMT+5:30), then the date and time in the device must be set to the current date and time in India. Clock drifts of a few minutes or more, or failure to adjust to daylight savings time changes, can cause the errors described in this article to occur. If the date and time appears to be correct, check to make sure the geographical region configured in the device is correct too.
We recommend setting mobile device times using the Auto feature in the device, if available, so that device times are automatically set accurately by the mobile network. Check with your mobile network provider to confirm if automatic clock setting is available. For devices that do not use a mobile network, RSA recommends configuring a reliable NTP server to automatically synchronize your computer's time.
Workaround
Notes
- For additional troubleshooting tips, see Troubleshooting Cloud Authentication Service User Issues .
- For instructions to set the date, time and geographical region, or to set the Auto option for time of day in your device, please refer to the vendor documentation of your device.
Related Articles
QR Code Failure After Replacing the Virtual Host Certificate 90Number of Views Convert a file-based RSA SecurID software token from .sdtid (CTF) format to a QR code failed with error "Java is not recog… 184Number of Views RSA SecurID Authenticate app registration fails on MIUI devices with error "Unsuccessful RSA SecurID Access Setup" 137Number of Views REMINDER: Mandatory Time-Bound Upgrade Required for RSA Authentication Manager and RSA Authenticate App/RSA Authenticator … 175Number of Views Registering Devices with the RSA Authenticator App 34Number of Views
Trending Articles
Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory Authentication Manager Security Console and Operations Console Inaccessible After Certificate Update
Don't see what you're looking for?