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 321Number of Views Allow a User to Authenticate Without an RSA SecurID PIN 54Number of Views After restarting RSA Identity Governance & Lifecycle, the browser shows an Initialization Status screen with connection er… 394Number of Views Unable to Resolve User by Login ID and/or Alias or Authenticator Not Assigned to User When Attempting to Authenticate via … 2.17KNumber of Views
Trending Articles
Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory Authentication Manager Security Console and Operations Console Inaccessible After Certificate Update
Don't see what you're looking for?