Intermittent LDAP.DirectoryUserLookup failure for New Experience realms

Version Affected:  [All Versions]

Description:  

LDAP.DirectoryUserLookup intermittently fails with "Exception: The user name or password is incorrect" for New Experience realms.

Cause:  

Issue occurs when the Data Store credential is configured with SamAccountName of the service account.

When the realm goes to sleep, requests get queued and domain suffix gets added multiple times to the service account, resulting in service_account@domain.com@domain.com.

Debug logs:

Message="LDAP.GetVaultCreds: _connectionUsername does not contain @" 
Message="LDAP.GetVaultCreds: _connectionUsername does not contain @" 
Message="LDAP.GetVaultCreds: _connectionUsername=service_account - _connectionDomain=@domain.com"
Message="LDAP.GetVaultCreds: _connectionUsername=service_account@domain.com"
Message="LDAP.GetVaultCreds: _connectionUsername=service_account@domain.com - _connectionDomain=@domain.com"
Message="LDAP.GetVaultCreds: _connectionUsername= service_account@domain.com@domain.com"

Resolution:  

Append the data store service account with the domain suffix in the new experience to eliminate the calls to add @domain.com to service account.

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.