Users cannot authenticate with login name in domain\sAMAccountName format using MFA Agent 2.0.1
Originally Published: 2021-03-11
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 Authentication Agent 7.2.1 for Windows cannot determine challenge group if the user submits fully qualified domain nam… Number of Views Trying to log in through Altiga VPN using Windows 2000 IPSEC Number of Views Enable a web proxy for RSA MFA Agent for Microsoft Windows Number of Views
Trending Articles
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 MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide Enable SSH from a console connection if the Operations Console is not available for RSA Authentication Manager 8.x RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows
Don't see what you're looking for?
