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 TERMINATION_DATE from Oracle HRMS Authentication System is not getting stored in RSA Identity Governance and Lifecycle 7.0 20Number of Views Kanbanize-SecurID-Access-SAML-Integration 2Number of Views How to use SearchFilterForAccounts when configuring an RSA Via Lifecycle & Governance Authentication Source 15Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide
Don't see what you're looking for?