Users cannot authenticate with login name in domain\sAMAccountName format using MFA Agent 2.0.1
Originally Published: 2021-03-11
Last Modified: 2022-08-30
Article Number
Applies To
RSA Product: RSA Authentication Agent for Windows
RSA Product: RSA AM 8.4 with CAS enabled.
Issue
CAS_domain users are able to authenticate using user@ad.cas_domain.com (UPN)When the MFA Agent was deployed, but cannot authneticate using login name in domain\sAMAccountName format with MFA Agent. The option to “Send Domain and User Name to RSA Authentication Manager” was disabled because the cloud tenant is unable to accept the username as “domain\sAMAccountName”.
Cause
Resolution
Download RSA Authentication MFA Agent: RSA® MFA Agent for Microsoft Windows Downloads
Documentation: RSA MFA Agent for Microsoft Windows Documentation
Related Articles
How to authenticate to an RSA Authentication Agent for Windows as user@domain.com with NTLM to UPN name mapping Number of Views Unchallenged Active Directory users fail to authenticate with RSA Authentication Agent for PAM Number of Views RSA Identity Governance & Lifecycle collector throws "Login failed. The login is from an untrusted domain and cannot be us… Number of Views After restarting RSA Identity Governance & Lifecycle, the browser shows an Initialization Status screen with connection er… Number of Views RSA MFA Agent 2.3 for Microsoft Windows Installation and Administration Guide Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Unable to login to RSA Authentication Manager Security Console as super admin RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Governance & Lifecycle 8.0.0 Installation Guide Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6
Don't see what you're looking for?
