The LDAP connector allows email/password based authentication, backed by a LDAP directory.
The connector executes two primary queries:
- Finding the user based on the end user’s credentials.
- Searching for groups using the user entry.
The dex repo contains a basic LDAP setup using OpenLDAP .
First start the LDAP server using docker-compose. This will run the OpenLDAP daemon in a Docker container, and seed it with an initial set of users.
cd examples/ldap docker-compose up
This container is expected to print several warning messages which are normal. Once the server is up, run dex in another terminal.
./bin/dex serve examples/ldap/config-ldap.yaml
Then run the OAuth client in another terminal.
, login and enter the username and password of the LDAP user:
foo. Add the “groups” scope as part of the initial redirect to add group information from the LDAP server.
Dex attempts to bind with the backing LDAP server using the end user’s plain text password. Though some LDAP implementations allow passing hashed passwords, dex doesn’t support hashing and instead strongly recommends that all administrators just use TLS. This can often be achieved by using port 636 instead of 389, and administrators that choose 389 are actively leaking passwords.
Dex currently allows insecure connections because the project is still verifying that dex works with the wide variety of LDAP implementations. However, dex may remove this transport option, and users who configure LDAP login using 389 are not covered by any compatibility guarantees with future releases.
User entries are expected to have an email attribute (configurable through
emailAttr), and a display name attribute (configurable through
*Attr attributes could be set to “DN” in situations where it is needed but not available elsewhere, and if “DN” attribute does not exist in the record.
For the purposes of configuring this connector, “DN” is case-sensitive and should always be capitalised.
The following is an example config file that can be used by the LDAP connector to authenticate a user.
connectors: - type: ldap # Required field for connector id. id: ldap # Required field for connector name. name: LDAP config: # Host and optional port of the LDAP server in the form "host:port". # If the port is not supplied, it will be guessed based on "insecureNoSSL", # and "startTLS" flags. 389 for insecure or StartTLS connections, 636 # otherwise. host: ldap.example.com:636 # Following field is required if the LDAP host is not using TLS (port 389). # Because this option inherently leaks passwords to anyone on the same network # as dex, THIS OPTION MAY BE REMOVED WITHOUT WARNING IN A FUTURE RELEASE. # # insecureNoSSL: true # If a custom certificate isn't provide, this option can be used to turn on # TLS certificate checks. As noted, it is insecure and shouldn't be used outside # of explorative phases. # # insecureSkipVerify: true # When connecting to the server, connect using the ldap:// protocol then issue # a StartTLS command. If unspecified, connections will use the ldaps:// protocol # # startTLS: true # Path to a trusted root certificate file. Default: use the host's root CA. rootCA: /etc/dex/ldap.ca # A raw certificate file can also be provided inline. # rootCAData: ( base64 encoded PEM file ) # The DN and password for an application service account. The connector uses # these credentials to search for users and groups. Not required if the LDAP # server provides access for anonymous auth. # Please note that if the bind password contains a `$`, it has to be saved in an # environment variable which should be given as the value to `bindPW`. bindDN: uid=serviceaccount,cn=users,dc=example,dc=com bindPW: password # The attribute to display in the provided password prompt. If unset, will # display "Username" usernamePrompt: SSO Username # User search maps a username and password entered by a user to a LDAP entry. userSearch: # BaseDN to start the search from. It will translate to the query # "(&(objectClass=person)(uid=<username>))". baseDN: cn=users,dc=example,dc=com # Optional filter to apply when searching the directory. filter: "(objectClass=person)" # username attribute used for comparing user entries. This will be translated # and combined with the other filter as "(<attr>=<username>)". username: uid # The following three fields are direct mappings of attributes on the user entry. # String representation of the user. idAttr: uid # Required. Attribute to map to Email. emailAttr: mail # Maps to display name of users. No default value. nameAttr: name # Maps to preferred username of users. No default value. preferredUsernameAttr: uid # Group search queries for groups given a user entry. groupSearch: # BaseDN to start the search from. It will translate to the query # "(&(objectClass=group)(member=<user uid>))". baseDN: cn=groups,dc=freeipa,dc=example,dc=com # Optional filter to apply when searching the directory. filter: "(objectClass=group)" # Following list contains field pairs that are used to match a user to a group. It adds an additional # requirement to the filter that an attribute in the group must match the user's # attribute value. userMatchers: - userAttr: uid groupAttr: member # Represents group name. nameAttr: name
The LDAP connector first initializes a connection to the LDAP directory using the
bindPW. It then tries to search for the given
username and bind as that user to verify their password.
Searches that return multiple entries are considered ambiguous and will return an error.
Writing a search configuration often involves mapping an existing LDAP schema to the various options dex provides. To query an existing LDAP schema install the OpenLDAP tool
rpm based distros run:
sudo dnf install openldap-clients
sudo apt-get install ldap-utils
For smaller user directories it may be practical to dump the entire contents and search by hand.
ldapsearch -x -H ldap://ldap.example.org -b 'dc=example,dc=org' | less
First, find a user entry. User entries declare users who can login to LDAP connector using username and password.
dn: uid=jdoe,cn=users,cn=compat,dc=example,dc=org cn: Jane Doe objectClass: posixAccount objectClass: ipaOverrideTarget objectClass: top gidNumber: 200015 gecos: Jane Doe uidNumber: 200015 loginShell: /bin/bash homeDirectory: /home/jdoe mail: email@example.com uid: janedoe
Compose a user search which returns this user.
userSearch: # The directory directly above the user entry. baseDN: cn=users,cn=compat,dc=example,dc=org filter: "(objectClass=posixAccount)" # Expect user to enter "janedoe" when logging in. username: uid # Use the full DN as an ID. idAttr: DN # When an email address is not available, use another value unique to the user, like uid. emailAttr: mail nameAttr: gecos
Second, find a group entry.
dn: cn=developers,cn=groups,cn=compat,dc=example,dc=org memberUid: janedoe memberUid: johndoe gidNumber: 200115 objectClass: posixGroup objectClass: ipaOverrideTarget objectClass: top cn: developers
Group searches must match a user attribute to a group attribute. In this example, the search returns users whose uid is found in the group’s list of memberUid attributes.
groupSearch: # The directory directly above the group entry. baseDN: cn=groups,cn=compat,dc=example,dc=org filter: "(objectClass=posixGroup)" # The group search needs to match the "uid" attribute on # the user with the "memberUid" attribute on the group. userMatchers: - userAttr: uid groupAttr: memberUid # Unique name of the group. nameAttr: cn
To extract group specific information the
DN can be used in the
# Top level object example.coma in LDIF file. dn: dc=example,dc=com objectClass: top objectClass: dcObject objectClass: organization dc: example
The following is an example of a group query would match any entry with member=:
groupSearch: # BaseDN to start the search from. It will translate to the query # "(&(objectClass=group)(member=<user DN>))". baseDN: cn=groups,cn=compat,dc=example,dc=com # Optional filter to apply when searching the directory. filter: "(objectClass=group)" userMatchers: - userAttr: DN # Use "DN" here not "uid" groupAttr: member nameAttr: name
There are cases when different types (objectClass) of groups use different attributes to keep a list of members. Below is an example of group query for such case:
groupSearch: baseDN: cn=groups,cn=compat,dc=example,dc=com # Optional filter to search for different group types filter: "(|(objectClass=posixGroup)(objectClass=group))" # Use multiple user matchers so Dex will know which attribute names should be used to search for group members userMatchers: - userAttr: uid groupAttr: memberUid - userAttr: DN groupAttr: member nameAttr: name
The following configuration will allow the LDAP connector to search a FreeIPA directory using an LDAP filter.
connectors: - type: ldap id: ldap name: LDAP config: # host and port of the LDAP server in form "host:port". host: freeipa.example.com:636 # freeIPA server's CA rootCA: ca.crt userSearch: # Would translate to the query "(&(objectClass=posixAccount)(uid=<username>))". baseDN: cn=users,dc=freeipa,dc=example,dc=com filter: "(objectClass=posixAccount)" username: uid idAttr: uid # Required. Attribute to map to Email. emailAttr: mail # Entity attribute to map to display name of users. groupSearch: # Would translate to the query "(&(objectClass=group)(member=<user uid>))". baseDN: cn=groups,dc=freeipa,dc=example,dc=com filter: "(objectClass=group)" userMatchers: - userAttr: uid groupAttr: member nameAttr: name
If the search finds an entry, it will attempt to use the provided password to bind as that user entry.
The following configuration will allow the LDAP connector to search a Active Directory using an LDAP filter.
connectors: - type: ldap name: ActiveDirectory id: ad config: host: ad.example.com:636 insecureNoSSL: false insecureSkipVerify: true bindDN: cn=Administrator,cn=users,dc=example,dc=com bindPW: admin0! usernamePrompt: Email Address userSearch: baseDN: cn=Users,dc=example,dc=com filter: "(objectClass=person)" username: userPrincipalName idAttr: DN emailAttr: userPrincipalName nameAttr: cn groupSearch: baseDN: cn=Users,dc=example,dc=com filter: "(objectClass=group)" userMatchers: - userAttr: DN groupAttr: member nameAttr: cn