authentik icon indicating copy to clipboard operation
authentik copied to clipboard

`object uniqueness field` should be explicitly listed as attribute when querying LDAP

Open saz opened this issue 1 year ago • 0 comments

Describe the bug Although while fetching users from LDAP attributes are set to [ALL_ATTRIBUTES, ALL_OPERATIONAL_ATTRIBUTES], the field used for object uniqueness might still not be a part of returned attributes.

{"attributes": "dict_keys(['objectClass', 'uid', 'googleUid', 'posixUid', 'cn', 'sn', 'displayName', 'givenName', 'mail', 'title', 'employeeNumber', 'employeeType', 'departmentNumber', 'physicalDeliveryOfficeName', 'uidNumber', 'gidNumber', 'homeDirectory', 'loginShell', 'gecos', 'telephoneNumber', 'suspended', 'apple-generateduid', 'memberOf'])", "dn": "uid=some.user,ou=someOu,ou=Users,dc=example,dc=com", "domain_url": null, "event": "Cannot find uniqueness field in attributes: 'uid=some.user,ou=someOub,ou=Users,dc=example,dc=com'", "level": "warning", "logger": "authentik.sources.ldap.sync.base", "pid": 7, "schema_name": "public", "source": "<LDAPSource: Google LDAP>", "syncer": "UserLDAPSynchronizer", "timestamp": "2024-08-29T11:37:23.705844"}

To Reproduce Steps to reproduce the behavior:

  1. Set up Google Secure LDAP as LDAP source
  2. Trigger a sync

Expected behavior Users are getting synced properly

Screenshots N/A

Logs See above

Version and Deployment (please complete the following information):

  • authentik version: 2024.6.4
  • Deployment: docker-compose

Additional context Add any other context about the problem here.

saz avatar Aug 29 '24 12:08 saz