Skip to content

Authenticating against an LDAP server

Warning: You are browsing the documentation for Symfony 2.x, which is no longer maintained.

Read the updated version of this page for Symfony 7.1 (the current stable version).

Symfony provides different means to work with an LDAP server.

The Security component offers:

  • The ldap user provider, using the LdapUserProvider class. Like all other user providers, it can be used with any authentication provider.
  • The form_login_ldap authentication provider, for authenticating against an LDAP server using a login form. Like all other authentication providers, it can be used with any user provider.
  • The http_basic_ldap authentication provider, for authenticating against an LDAP server using HTTP Basic. Like all other authentication providers, it can be used with any user provider.

This means that the following scenarios will work:

  • Checking a user's password and fetching user information against an LDAP server. This can be done using both the LDAP user provider and either the LDAP form login or LDAP HTTP Basic authentication providers.
  • Checking a user's password against an LDAP server while fetching user information from another source (database using FOSUserBundle, for example).
  • Loading user information from an LDAP server, while using another authentication strategy (token-based pre-authentication, for example).

Ldap Configuration Reference

See Security Configuration Reference (SecurityBundle) for the full LDAP configuration reference (form_login_ldap, http_basic_ldap, ldap). Some of the more interesting options are explained below.

Configuring the LDAP client

All mechanisms actually need an LDAP client previously configured. The providers are configured to use a default service named ldap, but you can override this setting in the security component's configuration.

An LDAP client can be simply configured, using the following service definition:

1
2
3
4
5
6
7
8
9
10
# app/config/services.yml
services:
    ldap:
        class: Symfony\Component\Ldap\LdapClient
        arguments:
            - my-server   # host
            - 389         # port
            - 3           # version
            - false       # SSL
            - true        # TLS

Fetching Users Using the LDAP User Provider

If you want to fetch user information from an LDAP server, you may want to use the ldap user provider.

1
2
3
4
5
6
7
8
9
10
11
12
13
# app/config/security.yml
security:
    # ...

    providers:
        my_ldap:
            ldap:
                service: ldap
                base_dn: dc=example,dc=com
                search_dn: "cn=read-only-admin,dc=example,dc=com"
                search_password: password
                default_roles: ROLE_USER
                uid_key: uid

Caution

The Security component escapes provided input data when the LDAP user provider is used. However, the LDAP component itself does not provide any escaping yet. Thus, it's your responsibility to prevent LDAP injection attacks when using the component directly.

Caution

The user configured above in the the user provider is only used to retrieve data. It's a static user defined by its username and password (for improved security, define the password as an environment variable).

If your LDAP server allows to retrieve information anonymously, you can set the search_dn and search_password options to null.

The ldap user provider supports many different configuration options:

service

type: string default: ldap

This is the name of your configured LDAP client. You can freely chose the name, but it must be unique in your application and it cannot start with a number or contain white spaces.

base_dn

type: string default: null

This is the base DN for the directory

search_dn

type: string default: null

This is your read-only user's DN, which will be used to authenticate against the LDAP server in order to fetch the user's information.

search_password

type: string default: null

This is your read-only user's password, which will be used to authenticate against the LDAP server in order to fetch the user's information.

default_roles

type: array default: []

This is the default role you wish to give to a user fetched from the LDAP server. If you do not configure this key, your users won't have any roles, and will not be considered as authenticated fully.

uid_key

type: string default: sAMAccountName

This is the entry's key to use as its UID. Depends on your LDAP server implementation. Commonly used values are:

  • sAMAccountName
  • userPrincipalName
  • uid

filter

type: string default: ({uid_key}={username})

This key lets you configure which LDAP query will be used. The {uid_key} string will be replaced by the value of the uid_key configuration value (by default, sAMAccountName), and the {username} string will be replaced by the username you are trying to load.

For example, with a uid_key of uid, and if you are trying to load the user fabpot, the final string will be: (uid=fabpot).

Of course, the username will be escaped, in order to prevent LDAP injection.

The syntax for the filter key is defined by RFC4515.

Authenticating against an LDAP server

Authenticating against an LDAP server can be done using either the form login or the HTTP Basic authentication providers.

They are configured exactly as their non-LDAP counterparts, with the addition of two configuration keys:

service

type: string default: ldap

This is the name of your configured LDAP client. You can freely chose the name, but it must be unique in your application and it cannot start with a number or contain white spaces.

dn_string

type: string default: {username}

This key defines the form of the string used in order to compose the DN of the user, from the username. The {username} string is replaced by the actual username of the person trying to authenticate.

For example, if your users have DN strings in the form uid=einstein,dc=example,dc=com, then the dn_string will be uid={username},dc=example,dc=com.

Examples are provided below, for both form_login_ldap and http_basic_ldap.

Configuration example for form login

1
2
3
4
5
6
7
8
9
10
11
12
13
# app/config/security.yml
security:
    # ...

    firewalls:
        main:
            # ...
            form_login_ldap:
                login_path: login
                check_path: login_check
                # ...
                service: ldap
                dn_string: 'uid={username},dc=example,dc=com'

Configuration example for HTTP Basic

1
2
3
4
5
6
7
8
9
10
11
# app/config/security.yml
security:
    # ...

    firewalls:
        main:
            # ...
            http_basic_ldap:
                # ...
                service: ldap
                dn_string: 'uid={username},dc=example,dc=com'
This work, including the code samples, is licensed under a Creative Commons BY-SA 3.0 license.
TOC
    Version