Skip to content

Commit 77c55b2

Browse files
committed
Merge branch '3.4' into 4.2
* 3.4: [Ldap] minor: better query string docs
2 parents 53318e1 + bcb245e commit 77c55b2

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

security/ldap.rst

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -330,12 +330,12 @@ providers with different ``base_dn``. The value of this option must be a valid
330330
search string (e.g. ``uid="{username}"``). The placeholder value will be
331331
replaced by the actual username.
332332

333-
When this option is used, ``dn_string`` has to be updated accordingly. Following
334-
the previous example, if your users have the following two DN:
335-
``dc=companyA,dc=example,dc=com`` and ``dc=companyB,dc=example,dc=com``, then
336-
``dn_string`` should be ``dc=example,dc=com``. If the ``query_string`` option is
337-
``uid="{username}"``, then the authentication provider can authenticate users
338-
from both DN.
333+
When this option is used, ``query_string`` will search in the DN specified by
334+
``dn_string`` and the DN resulted of the ``query_string`` will be used to
335+
authenticate the user with their password. Following the previous example, if
336+
your users have the following two DN: ``dc=companyA,dc=example,dc=com`` and
337+
``dc=companyB,dc=example,dc=com``, then ``dn_string`` should be
338+
``dc=example,dc=com``.
339339

340340
Bear in mind that usernames must be unique across both DN, as the authentication
341341
provider won't be able to select the correct user for the bind process if more

0 commit comments

Comments
 (0)