Hello @terpstra !
I wanted to do some research on this topic since I thought it was a pretty interesting problem you were having.
I found this section from our Help page (https://help.acumatica.com/(W(7))/Wiki/ShowWiki.aspx?pageid=8475a118-8bcd-40fb-99ef-cf9fda54f744):
“Generally, to sign in to Acumatica ERP, AD users type their domain credentials without specifying the domain name. But some employees may have both a local user account and a domain user account with the same user name. In this case, Acumatica ERP will authenticate the users based on the password they specify (assuming that the local and domain passwords differ).
If both the user names and the passwords are the same for a local user account and a domain user account, on the Sign-In page, the user can select the account to sign in with as follows:
- To sign in with a local account, the user enters the user name of the local account (as usual).
- To sign in with a domain account, the user enters the login in the <Domain_Name>\<User_Name> format, where <Domain_Name> is the NetBIOS domain name of the integrated domain and <User_Name> is the user account name in the integrated domain.”
And:
| If there is a local account with the name which includes a domain name and a user name from this domain, for example, Terra\User1, a domain user with the name User1 from domain Terra will be mapped to this local account and will inherit all permissions of this account. In this case passwords of a local user and a domain user may differ but they both will access the same user account. To prevent confusion, we recommend that you disable or delete the local accounts of employees who do not perform any administration or configuration tasks in Acumatica ERP. |
From the Help Page, it looks like the default behavior doesn’t require the domain\ in front of the username. Your situation will depend if there’s both a local and AD account that shares usernames. Let me know if this information helps out, thanks!
@VladS it sure does. So if I understand that correctly, it will always query AD and the failed login attempts are to be expected.
As for logging in without the domain\, I was unable to do so. Probably a configuration issue on our end but I’ll look into it further.