Server: LDAP: can not find user when name and surname are empty on AD-user-object

[victorbw]

Sometimes it happens or is mandatory that some LDAP users (Microsoft Server 2016 in this case), like admins or other technical accounts, do NOT have any name or surname in the object listed.

Nextcloud version (eg, 12.0.2): 14.0.3
Operating system and version (eg, Ubuntu 17.04): ubuntu 16.04LTS
Apache or nginx version (eg, Apache 2.4.25): apache 2.4.18
PHP version (eg, 7.1): 7.0

The issue you are facing: nc-ldap is not showing any user who has empty name & surname fields.

Is this the first time you’ve seen this error? (Y/N): Y

Steps to replicate it:

create AD-User
remove users name/surname
rescan AD
users without name/surname wont be listed at all and therefore cannot log in

So the questions are:

Is this a behaviour by design or simply got forgotten to cover? Haven't found any information about this so far.
Anyone else seen the same issue?
Is there a workaround for this, except for filling name and surname into AD-Object?

thanks in advance! :wink:

[nextcloud-bot]

GitMate.io thinks possibly related issues are https://github.com/nextcloud/server/issues/7510 (User is not found when is searched by name and one of surnames), https://github.com/nextcloud/server/issues/5577 (Cannot delete User which is deleted in LDAP), https://github.com/nextcloud/server/issues/6719 (Changing LDAP user Full Name), https://github.com/nextcloud/server/issues/12229 (LDAP Searches in Sharing Returning Duplicates and Disabled User Objects), and https://github.com/nextcloud/server/pull/8760 (User is not found when is searched by name and one of surnames #7510).

[blizzz]

The issue you are facing: nc-ldap is not showing any user who has empty name & surname fields.

To be precise, it does not import any user with a missing displayname attribute (as configured).

So, yes, this is by design, to (reliably…) avoid pulling in various system accounts.

[ChristophWurst]

Sooo … wontfix?

[blizzz]

Yeah, essentially, yes.

[victorbw]

Maybe this should be mentioned in the documentation as a side-note - just in case?

[blizzz]

@victorbw i thought it was, but apparently it is not, indeed. Would you like to try to bring it in? → https://github.com/nextcloud/documentation/blob/master/admin_manual/configuration_user/user_auth_ldap.rst

[victorbw]

@victorbw i thought it was, but apparently it is not, indeed. Would you like to try to bring it in? → https://github.com/nextcloud/documentation/blob/master/admin_manual/configuration_user/user_auth_ldap.rst

If there's no stress to be done within a few days, sure, why not :)

Hope I'll do it right - just planting a new pull-request should do it, right?

[ChristophWurst]

Hope I'll do it right - just planting a new pull-request should do it, right?

Yes! Thank you!

[victorbw]

moved to #1010