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 519Number of Views Unchallenged Active Directory users fail to authenticate with RSA Authentication Agent for PAM 316Number of Views env: cluster setup Creating the cluster......System error 1326 has occurred (0x0000052e). 31Number of Views Access Manager is unable to connect to Active Directory even after expired Domain Controller certificate is replaced 42Number of Views Check Point on Nokia appliances not able to authenticate users with RSA SecurID 29Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA-2026-10: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA SecurID Desktop Token 5.0.3 for Windows Administrator's Guide RSA SecurID Software Token 4.2.1 for Mac OS X Administrator's Guide
Don't see what you're looking for?