Symptoms

  • The domain's DNS name differs from the UPN suffix users sign in with. For example, the AD domain is corp.local and users sign in as user@example.com.
  • The console's test page fails for user@example.com with "Failed to initialize LDAP session ... for the example.com domain.", but works for CORP\user.
  • The Workstation Client may not show password requirements for these users.

Cause

Enzoic currently looks up its settings in a domain named after the UPN suffix. Alternate UPN suffixes aren't supported yet.


Workaround

When using the console's test page or on a change password screen, enter the user as DOMAIN\username.