Unsuccessful connection to RSA SecurID Access: Authentication token was either missing or invalid
Originally Published: 2023-03-03
Article Number
Applies To
RSA Product/Service Type: RSA MFA Agent for Microsoft Windows
RSA Version/Condition: 2.1.x
Issue
ApiException occurred: IO.Swagger.AuthenticationClient.ApiException: Error calling Initialize: Unauthorized: Authentication token was either missing or invalid.
Cause
Resolution
2. Run regedit.msc
3. Navigate to the Registry Key HKEY_LOCAL_MACHINE\SOFTWARE\Policies\RSA\RSA Desktop\CAS Authentication Settings\Authentication Server Settings
4. Update the value manually with the correct Access key
5. From the cmd => Run gpupdate /force as an Administrator
Workaround
Notes
Related Articles
Misleading Unsuccessful Authentication Display 101Number of Views Troubleshooting "unsuccessful logon" failure for the SecurID Access Portal 165Number of Views Troubleshooting RSA SecurID Access Application Portal unsuccessful logon message due to a bad identity source bind 334Number of Views Common questions regarding RSA SecurID tokens and access to RSA technical support 529Number of Views How to set emergency access tokencode lifetime for permanently lost or broken RSA SecurID tokens 480Number of Views
Trending Articles
How to Download OTP Token Seed Files from myRSA RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Release Notes for RSA Authentication Manager 8.8
Don't see what you're looking for?