Domain account authentication to vIDM fails with "incorrect username/password" errors for all domain user IDs, despite confirming the credentials are valid.
A review of the /opt/vmware/horizon/workspace/logs/horizon.log reveals following events:
com. vmware. horizon. directory. ldap. LdapDirectoryService - User <Username> not found under base DN - FAILURE
com. vmware. horizon. adapters.passwordAdapter. PasswordIdpAdapter - attribute : email
com. vmware . horizon. adapters . passwordAdapter. PasswordIdpAdapter - User Email attribute :
com. vmware. horizon. adapters . passwordAdapter. PasswordIdpAdapter - outside if email HIDDEN
com. vmware . horizon. adapters. passwordAdapter. PasswordIdpAdapter - attribute : userInput
com. vmware. horizon. adapters . passwordAdapter . PasswordIdpAdapter - outside if userInput HIDDEN
VMware Identity Manager 3.3.7
Domain authentication fails because Active Directory is synchronized using the userPrincipalName (UPN) rather than the sAMAccountName.
To resolve this issue, ensure you are using the correct username format based on your Active Directory synchronization method:
If synced via SAM Account Name: Enter the username in the standard USERNAME format.
If synced via User Principal Name (UPN): Enter the username in the USERNAME@DOMAIN format. A UPN combines the user account name (prefix) and the DNS domain name (suffix) separated by an @ symbol (for example, [email protected]).