Skip to content

Failed to load groups with LDAP auth #216

@muzzol

Description

@muzzol

I can login with my LDAP user but groups are not fetched. I get this line when I log in:

2019-05-17 13:48:31,667 [script_server.LdapAuthorizer.INFO] Logging in user u100001
2019-05-17 13:48:31,673 [script_server.LdapAuthorizer.ERROR] Failed to load groups for the user u100001
Traceback (most recent call last):
  File "src/auth/auth_ldap.py", line 114, in authenticate
    user_dn, user_uid = self._get_user_ids(full_username, connection)
  File "src/auth/auth_ldap.py", line 206, in _get_user_ids
    return entry.entry_dn, entry.uid.value
  File "/usr/lib/python3/dist-packages/ldap3/abstract/entry.py", line 88, in __getattr__
    raise LDAPAttributeError('attribute not found')
ldap3.core.exceptions.LDAPAttributeError: attribute not found
2019-05-17 13:48:31,675 [script_server.tornado_auth.INFO] Authenticated user u100001

this is my conf

  "auth": {
    "type": "ldap",
    "url": "ldap://cabot.cilma.net",
    "username_pattern": "uid=$username,ou=persones,ou=users,dc=consorci,dc=global",
    "base_dn": "dc=consorci,dc=global",
    "version": 3

and I can login so LDAP connection is working.

It could be related my LDAP tree because I got some nested OUs.

Users are in this OU:

uid=u100001,ou=persones,ou=users,dc=consorci,dc=global

and groups are here:

cn=rol-app3,ou=rols,ou=groups,dc=consorci,dc=global

maybe an additional setting like group_base_dn could be useful (some apps do it that way to avoid any confusion with other parts of tree).

I'm testing it with 1.14

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions