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 92Number of Views A successful RSA Cloud Authentication Service OIDC authentication is rejected by the application due to id_token missing r… 81Number of Views The specified token type does not match the requested token type message when enabling token in the RSA Self-Service Console 33Number of Views Replica RADIUS not accepting authentication requests in RSA Authentication Manager 8.0 and 8.1 286Number of Views Troubleshooting "unsuccessful logon" failure for the SecurID Access Portal 151Number of Views
Trending Articles
RSA Release Notes for RSA Authentication Manager 8.8 RSA MFA Agent 2.4.3 for Microsoft Windows Group Policy Object Template Guide RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA MFA Agent 2.4.3 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026)
Don't see what you're looking for?