(10388 Admin Thread 1)UserStorage::LoginUserAD: Calling ValidateLogin DOMAIN\USER
(10388 Admin Thread 1)UserStorage::LoginUserAD: Check if canonical name '' exists
(10388 Admin Thread 1)ReportLogin called username = DOMAIN\USER, successful = 0
DEBUG ADHelper.ADInfo.GetDirectoryEntry - Bind successful with ldap path = LDAP://DOMAIN.TLD/CN=Protected User,CN=Users,DC=DOMAIN,DC=TLD
DEBUG ADHelper.ADInfo.GetADUserList - Found adUser for userName = DOMAIN\USER
DEBUG ADHelper.ADHandler.ParityServerADMapping - Computer = , Users = DOMAIN\USER, Ruleset = 2
Engineering is investigating this issue under EPCB-21147 and an official fix will be available in a future release of the Server.
The following temporary workaround can be used to force the "old logic" for Active Directory using vbscript. This should be reverted after upgrading to version where this issue is fixed.