LDAP import issue with domainname capitalization

Rene

Anybody noticed that when doing a LDAP import ( either a single user of full import) from the gui fails if the email address has a different capitalization than the domainname as entered on the domains page?

ie. if the domain is entered as Example.com , it shows in the domain list as Example.com(example.com) suggesting that all lowercase should also work, but when going into the domains/users/search LDAP-> specific user the import fails is the email address ends in @example.com, but succeeds if it's @Example.com.

Is this designed behaviour? I would expect the (mail) domain to be case-insensitive in receiving mail and in importing users.

I did try to search for this issue, but could find any ( or searched in the wrong places).

crpb

I can confirm that it breaks here too. With uppercase in the Domain it says it would be a foreign Domain and if i just change a char in the front part to an uppercase it says it can't import it due to an duplicate entry.

# USERNAME
Synchronizing cb@clownflare.de...Duplicate entry 'cB@otherdomain.de' for key 'PRIMARY'
# DOMAINNAME
Synchronizing cb@clownflare.de...Cannot use alias from foreign domain: cb@CLOWNFLARE.de

@jschroeder 👋

Rene

ok, thanks for confirming @crpb . Does it get added to the isssue list 'automatically' or do I need to add it on a list somewhere?

crpb

@Rene

I'm just a partner and not from grommunio. Thats why i "waved" at jschroeder(@grommunio).
Maybe i get around later to create an issue on github but only if i don't forget.

But if you have an account @github you could open an issue in the admin-api as thats where this is happening.

Steakie

@jschroeder isn't available right now, let's see if i can figure this out instead

Rene

Ok, well, i've got a github account, so I'll add it to the admin-api issue list. then at least its 'official' and @Steakie has a place to link his -possible- changes to.

edit:
Issue #42 https://github.com/grommunio/admin-api/issues/42

Steakie

Fixed. The update will be available soon

Rene

Great. thanks

Rene

It works for the import - only. The same issue exists if you add an smtp addres with dissimilar domain capitilization on the smtp page for the user

Steakie

Rene I am unable to reproduce this issue (wfm). However, there was another bug that you were unable to manually add capitalized smtp-addresses in AWEB which i just fixed. This might have solved your issue as well?

Rene

I seem to have messed up the appliance with the update, so i need to redeploy it before I can test. There is something that seems to be crashing, looks like a frontend issue but I probably created the issue myself being a windows server admin ;-)

Rene

I feel like i'm running into a similar issue as @ckd with the management interface, although in my case restarting the admin-api helps -a little- in making the interface active again, but as soon as I try to view the LDAP configuration , or perform an LDAP search the admin interface appears to 'hang', I can click other sections and they will respond, but when I try to refresh the page I need to log in again, which doesn't work until after the admin-api restart.

I did see an issue during the update of the appliance, php complains about an dependency "python311-flask" which is not available.

mail01:~ # zypper in grommunio-admin-api
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: 1: nothing provides 'python311-Flask' needed by the to be installed grommunio-admin-api-1.17.9.932eaca-lp156.310.1.noarch
 Solution 1: do not install grommunio-admin-api-1.17.9.932eaca-lp156.310.1.noarch
 Solution 2: break grommunio-admin-api-1.17.9.932eaca-lp156.310.1.noarch by ignoring some of its dependencies

Rene

Just done an update (zypper ref && zypper up on the appliance install with CE repositories), but this issue still exists (importing from AD with dissimilar capitalization).

Steakie

Rene What sort of LDAP are you using? I was unable to reproduce this with Univention

Rene

Windows AD user with the following proxy addresses;

name                       mail                        EmailAddresses
----                       ----                        --------------
Rene van den Broek-30Below Rene.vandenBroek@30Below.nl rene@30below.nl
                                                       rene.vandenbrok@30Below.nl
                                                       Rene.vandenBroek-30Below@30Below.nl

Mail domain was created as "30Below.nl". Adding the user from "domains/30Below.nl/users/search in LDAP" now fails on the "rene@30below.nl" alias.

Steakie

Problem found and fixed

Rene

great, gonna wait for the update and test it..

Steakie

Rene should be part of the community package now