8000 Explain the query_string ldap authentication provider configuration key by nietonfir · Pull Request #7414 · symfony/symfony-docs · GitHub
[go: up one dir, main page]
Skip to content

Explain the query_string ldap authentication provider configuration key #7414

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
Closed

Explain the query_string ldap authentication provider configuration key #7414

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7adcb87
Explain the query_string ldap authentication provider configuration key
Jan 26, 2017
6135043
Minor reword
javiereguiluz Jan 26, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
Explain the query_string ldap authentication provider configuration key 
Refs symfony/symfony#21402
  • Loading branch information
nietonfir committed Jan 26, 2017
commit 7adcb87932eb90192ed96d888868da6ee525056f
12 changes: 7 additions & 5 deletions reference/configuration/security.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -142,9 +142,10 @@ Each part will be explained in the next section.
http_basic:
provider: some_key_from_above
http_basic_ldap:
provider: some_key_from_above
service: ldap
dn_string: '{username}'
provider: some_key_from_above
service: ldap
dn_string: '{username}'
query_string: ~
http_digest:
provider: some_key_from_above
guard:
Expand Down Expand Up @@ -237,8 +238,9 @@ Each part will be explained in the next section.
# new in Symfony 2.3
require_previous_session: true

service: ~
dn_string: '{username}'
service: ~
dn_string: '{username}'
query_string: ~

remember_me:
token_provider: name
Expand Down
24 changes: 24 additions & 0 deletions security/ldap.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -270,6 +270,30 @@ 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``.

query_string
............

**type**: ``string``

This (optional) key enables the user provider to search for a user and
then use the DN found for the bind process. This is useful in environments
with multiple LDAP user providers with a different ``base_dn``. As value
a valid search string for should be used, e.g. ``uid="{username}"``. The
placeholder value will be replaced by the actual username.

When this key is used, ``dn_string`` has to be adjusted accordingly and
should reflect a common denominator as base DN.

Extending the previous example: If Your users have two different DN in the
form of ``dc=companyA,dc=example,dc=com`` and ``dc=companyB,dc=example,dc=com``,
then ``dn_string`` should be ``dc=example,dc=com``. In conjunction with
``uid="{username}"`` as ``query_string`` the authentication provider can
authenticate user from both DN.

Please bear in mind, that the usernames themselves have to be unique
across both DN, as the authentication provider won't determine the
correct user for the bind process if more than one are found.

Examples are provided below, for both ``form_login_ldap`` and
``http_basic_ldap``.

Expand Down
0