Win 2019 LDAP not working out of the box

bogdanor

Hello.

We configured fresh AD install on win 2019, added two users, but no success with importing users from AD.
Configured connector:

# grommunio-admin ldap
Successfully connected to 10.20.0.2:389 as ldapadmin@azxxxx.net
# grommunio-admin ldap search
ID Name E-Mail Type Note
\0c\92\9e\53\2e\43\42\46\97\5b\a7\40\55\1e\1d\4a Roman Bxxxxx roman.xxxx@azxxxx.net user
\ff\b6\6e\5f\2a\bd\50\43\ad\18\58\02\a0\2d\3f\55 Savva Oxxxxx savva.xxxx@azxxxx.net user
(3 results)

But cant import users at all.
Import button writes: Success! 0/0 synced (0.0s)

# grommunio-admin ldap downsync --complete -o 1
Importing user roman.xxxx@azxxxx.net...An error occurred: RuntimeError('Multiple entries found - aborting',).
# grommunio-admin ldap downsync roman.xxxx
An error occurred: TypeError("argument of type 'NoneType' is not iterable",).`

How to fix it? Why no additional checks(exept catches) inside ldap.py script?

# cat /etc/gromox/ldap_adaptor.cfg
$ Configuration automatically generated by grommunio-admin.
ldap_disabled=False
ldap_host=10.20.0.2
ldap_bind_user=ldapadmin@azxxxx.net
ldap_bind_pass=xxxx
ldap_start_tls=False
ldap_search_base=dc=azxxxx,dc=net
ldap_object_id=objectGUID
ldap_mail_attr=mail
ldap_user_displayname=displayName
ldap_user_filter=(&(objectClass=user))
ldap_contact_filter=objectclass=contact
ldap_user_search_attrs=mail
ldap_user_search_attrs=givenName
ldap_user_search_attrs=cn
ldap_user_search_attrs=sn
ldap_user_search_attrs=name
ldap_user_search_attrs=displayName
ldap_user_templates=common
ldap_user_templates=ActiveDirectory
ldap_user_aliases=proxyAddresses

# ldapsearch -h 10.20.0.2 -x -D ldapadmin@azxxxx.net -w xxxx -b "dc=azxxxx,dc=net" '(&(objectClass=user))' | grep "displayName|mail"
displayName: Roman Xxxx
mail: roman.xxxx@azxxxx.net
displayName: Savva Xxxx
mail: savva.xxxx@azxxxx.net
displayName: Ldap Admin

Packages are latest, fresh iso install:

i | grommunio | pattern | 1-lp153.8.1 | x86_64 | grommunio
i+ | grommunio-admin-api | package | 1.9.13.082efce-lp153.27.1 | noarch | grommunio
i+ | grommunio-admin-common | package | 6.cb985db-lp153.3.1 | noarch | (System Packages)
i+ | grommunio-admin-web | package | 2.6.0.16.969cf73-lp153.27.1 | noarch | grommunio
i+ | grommunio-antispam | package | 3.2-lp153.1.2 | x86_64 | (System Packages)
i+ | grommunio-common | package | 10.e94d08a-lp153.7.1 | x86_64 | grommunio
i+ | grommunio-cui | package | 1.0.91.6ca7863-lp153.25.1 | noarch | grommunio
i+ | grommunio-dav | package | 1.1.10.1e865f2-lp153.1.1 | noarch | grommunio
i+ | grommunio-dbconf | package | 1.1.1.da20a46-lp153.4.2 | x86_64 | (System Packages)
i | grommunio-error-pages | package | 1.0.6.9c50afb-lp153.3.1 | noarch | (System Packages)
i+ | grommunio-imapsync | package | 2.178-lp153.1.1 | noarch | (System Packages)
i+ | grommunio-index | package | 0.1.15.d3ec048-lp153.17.2 | x86_64 | grommunio
i+ | grommunio-release | package | 2022.05.2-lp153.1.1 | x86_64 | (System Packages)
i+ | grommunio-setup | package | 1.0.65.08008c8-lp153.5.1 | noarch | grommunio
i+ | grommunio-sync | package | 1.1.27-lp153.19.1 | noarch | grommunio
i+ | grommunio-web | package | 3.1.102.e70481f-lp153.56.1 | noarch | grommunio
i+ | gromox | package | 1.35.53.1016d84-lp153.160.1 | x86_64 | grommunio
i+ | gromox-debuginfo | package | 1.35.53.1016d84-lp153.160.1 | x86_64 | grommunio
i+ | gromox-debugsource | package | 1.35.53.1016d84-lp153.160.1 | x86_64 | grommunio

mwilliams

There has been some stray code in the community repository (see https://github.com/grommunio/admin-api/commit/927fb5a692d0e8e5bc82b78a1e4bcd12741b1e9d), Updates have been published and tester has confirmed with one of our AD installations. should be fine now.