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 95Number of Views How to set up a CRL Distribution Point in a certificate during certificate manual approval 8Number of Views Troubleshooting "unsuccessful logon" failure for the SecurID Access Portal 157Number of Views Troubleshooting RSA SecurID Access Application Portal unsuccessful logon message due to a bad identity source bind 321Number of Views Common questions regarding RSA SecurID tokens and access to RSA technical support 511Number of Views
Trending Articles
Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.9 Release Notes (January 2026) Artifacts to gather in RSA Identity Governance & Lifecycle RSA Governance & Lifecycle 8.0.0 Administrators Guide RSA Governance & Lifecycle 8.0.0 Installation Guide
Don't see what you're looking for?