authentik/website/docs/providers/ldap.md

title
LDAP Provider

You can configure an LDAP Provider for applications that don't support any newer protocols or require LDAP.

:::info Note: This provider requires the deployment of the LDAP Outpost :::

All users and groups in authentik's database are searchable. Currently, there is limited support for filters (you can only search for objectClass), but this will be expanded in further releases.

Binding against the LDAP Server uses a flow in the background. This allows you to use the same policies and flows as you do for web-based logins. For more info, see Bind modes.

You can configure under which base DN the information should be available. For this documentation we'll use the default of DC=ldap,DC=goauthentik,DC=io.

Users are available under ou=users,<base DN> and groups under ou=groups,<base DN>. To aid compatibility, each user belongs to its own "virtual" group, as is standard on most Unix-like systems. This group does not exist in the authentik database, and is generated on the fly. These virtual groups are under the ou=virtual-groups,<base DN> DN.

You can bind using the DN cn=<username>,ou=users,<base DN>, or using the following ldapsearch command for example:

ldapsearch \
  -x \ # Only simple binds are currently supported
  -h *ip* \
  -p 389 \
  -D 'cn=*user*,ou=users,DC=ldap,DC=goauthentik,DC=io' \ # Bind user and password
  -w '*password*' \
  -b 'ou=users,DC=ldap,DC=goauthentik,DC=io' \ # The search base
  '(objectClass=user)'

The following fields are currently sent for users:

• cn: User's username
• uid: Unique user identifier
• uidNumber: A unique numeric identifier for the user
• name: User's name
• displayName: User's name
• mail: User's email address
• objectClass: A list of these strings:
  • "user"
  • "organizationalPerson"
  • "goauthentik.io/ldap/user"
• memberOf: A list of all DNs that the user is a member of
• goauthentik.io/ldap/active: "true" if the account is active, otherwise "false"
• goauthentik.io/ldap/superuser: "true" if the account is part of a group with superuser permissions, otherwise "false"

The following fields are current set for groups:

• cn: The group's name
• uid: Unique group identifier
• gidNumber: A unique numeric identifier for the group
• member: A list of all DNs of the groups members
• objectClass: A list of these strings:
  • "group"
  • "goauthentik.io/ldap/group"

A virtual group is also created for each user, they have the same fields as groups but have an additional objectClass: goauthentik.io/ldap/virtual-group. The virtual groups gidNumber is equal to the uidNumber of the user.

Additionally, for both users and (non-virtual) groups, any attributes you set are also present as LDAP Attributes.

:::info Starting with 2021.9.1, custom attributes will override the inbuilt attributes. :::

SSL

You can also configure SSL for your LDAP Providers by selecting a certificate and a server name in the provider settings.

This enables you to bind on port 636 using LDAPS, StartTLS is not supported.

Integrations

See the integration guide for sssd for an example guide.

Bind Modes

All bind modes rely on flows.

The following stages are supported:

• Identification

• Password

• Authenticator validation

  Note: Authenticator validation currently only supports DUO devices

Direct bind

In this mode, the outpost will always execute the configured flow when a new bind request arrives.

Cached bind

This mode uses the same logic as direct bind, however the result is cached for the entered credentials, and saved in memory for the standard session duration. Sessions are saved independently, meaning that revoking sessions does not remove them from the outpost, and neither will changing a users credentials.

Search Modes

Direct search

Every LDAP search request will trigger one or more requests to the authentik core API. This will always return the latest data, however also has a performance hit due all the layers the backend requests have to go through, etc.

Cached search

In this mode, the outpost will periodically fetch all users and groups from the backend, hold them in memory, and respond to search queries directly. This means greatly improved performance but potentially returning old/invalid data.