LDAP AD import organization not set


  • Used Zammad version: 5.4 (also in earlier versions)

  • Used Zammad installation type: package

  • Operating system: Ubuntu Server 20.04 LTS

  • Browser + version: -

  • LDAP integration configured with Windows AD, Domain has multiple TLDs configured

  • Zammad login is mapped from userPrincipalName: username@mycompany.net

  • Organization “My Company” configured: mycompany.net

  • Organization Domain based assigment is activated

  • User import running without errors

Expected behavior:

  • LDAP import map new users the organization → “My Company”

Actual behavior:

  • New AD users are not mapped to the organization → “-”
  • Delete and rerun the import maps the organization → “My Company”

Steps to reproduce the behavior:

  • Microsoft AD configured, LDAP configured, Organization configured, domain based configured
  • User mapping zammad login ↔ userPrincipalName
  • Import AD User → new zammad account is created (here company is “-”)
  • Delete the user by rails command line
  • Import LDAP again
  • User has correct assigned company “My Company”

The domain based assignment does not affect login but email addresses.
Creating a new user (e.g. manually to verify this…) with a fitting mail address should automatically assign the user to that organisation. If that’s not the case, the organizations configuration might not be correct (e.g. assignment being “off”).

The domain based assignment does not affect login but email addresses.

Thank you! Thats the point. When creating a new user in AD with mail-address attribute everything works.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.