SID800-based Token fails with the Error - “Authentication failed because tokencode could not be read from connected token” in RSA Authentication Manager 8.1
Originally Published: 2016-07-04
Article Number
Applies To
Product/Service Type: Authentication Manager
RSA Version/Condition: 8.1
RSA Agent: 7.2.1
RSA SecurID SID800 Authenticator (USB token)
RSA Smart Card Middleware 3.6
RSA SecurID Software Token 5.0
Issue
“Authentication failed because tokencode could not be read from connected token”
Cause
Resolution
1] Ensure the RSA Agent 7.2 for Windows is installed. The software can be availed from the Official RSA Website (www.rsa.com)
NOTE: Ensure to install the LAC Agent in Custom Mode by enabling the "Connected Authenticator" feature, as shown below:
2] Ensure the RSA Authentication Client 3.6 is installed. This software is available at the URL below:
https://knowledge.rsasecurity.com/scolcms/sets.aspx?_v=download&product=hardware_token
3] Ensure RSA SecurID Software Token 5.0 for Microsoft Windows is installed with automation. The software can be availed from the official RSA Website (www.rsa.com)
Notes
[a] Insert the SID800 token on the Windows machine.
[b] Launch the RSA Control Center > SecurID Settings > Advanced Tools > Test Authentication
[c] Enter the following data:
User Name = <Appropriate User ID of the SID800 user>
SecurID PIN = <PIN associated with the corresponding SID800 token>
[d] Click "OK"
The authentication should succeed without the error message.
For a PIN-less authentication using SID800, perform the following steps:
[a] Insert the SID800 token on the Windows machine.
[b] Launch the RSA Control Center > SecurID Settings > Advanced Tools > Test Authentication
[c] Enter the following data:
User Name = <Appropriate User ID of the SID800 user>
SecurID PIN = <leave blank>
[d] Click "OK"
The authentication should succeed without the error message.
Related Articles
How to determine which firmware version is on an RSA SecurID SID800 authenticator 31Number of Views When configuring fob-style token profile, the token is configured as PINPad-style when using RSA Authentication Manager 8.… 63Number of Views How do you use a SID800 with multiple certificates and Windows credential provider? 66Number of Views Intermittent blinking of the RSA SecurID SID 800 token 87Number of Views Error occured in RSA Federated Identity Manger (FIM) 4.1 'Unable to verify the signature value' error when processing asse… 26Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) RSA announces the availability of the RSA SecurID Hardware Appliance 230 based on the Dell PowerEdge R240 Server How to troubleshoot Oracle database ORA-04030 errors in RSA Identity Governance & Lifecycle RSA Authentication Manager Upgrade Process Microsoft SQL Server Collectors can no longer connect to the SQL Server database after upgrade to Microsoft SQL Server 201…
Don't see what you're looking for?