goauthentik/authentik

Nested user attributes not exposed as valid LDAP attributes in LDAP Outpost

Open

#16.954 aberto em 23 de set. de 2025

Ver no GitHub
 (2 comments) (0 reactions) (0 assignees)Python (319 forks)batch import
bugbug/confirmedgood first issue

Métricas do repositório

Stars
 (4.050 stars)
Métricas de merge de PR
 (Mesclagem média 4d 6h) (627 fundiu PRs em 30d)

Description

Describe the bug When exposing custom attributes via the LDAP outpost, nested attributes are not returned as individual LDAP attributes. Instead, they appear in a serialized map format that does not seem to comply with LDAP.

To Reproduce Steps to reproduce the behavior:

  1. Configure a user in Authentik with a custom attribute containing nested values, e.g. settings.locale = en.
  2. Query the user via the LDAP outpost using ldapsearch.
  3. Inspect the LDAP response.

See that the attribute is returned as a serialized map string rather than as a proper multi-valued LDAP attribute.

Expected behavior I would expect the LDAP outpost to flatten or map the nested attribute into standard LDAP attributes, for example:

settingsLocale: en

or

settings.locale: en

instead of:

settings: map[locale:en]

Version and Deployment (please complete the following information):

  • authentik version: 2025.8.3
  • Deployment: Docker

Additional context Add any other context about the problem here.

Guia do colaborador