Skip to content

Commit bcb245e

Browse files
committed
Minor tweak
1 parent 1b7cc05 commit bcb245e

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

security/ldap.rst

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

316-
When this option is used, ``query_string`` will search in the DN specified by ``dn_string``
317-
and the DN resulted of the ``query_string`` will be used to authenticate the user with
318-
their password. Following the previous example, if your users have the following two DN:
319-
``dc=companyA,dc=example,dc=com`` and ``dc=companyB,dc=example,dc=com``, then
320-
``dn_string`` should be ``dc=example,dc=com``.
316+
When this option is used, ``query_string`` will search in the DN specified by
317+
``dn_string`` and the DN resulted of the ``query_string`` will be used to
318+
authenticate the user with their password. Following the previous example, if
319+
your users have the following two DN: ``dc=companyA,dc=example,dc=com`` and
320+
``dc=companyB,dc=example,dc=com``, then ``dn_string`` should be
321+
``dc=example,dc=com``.
321322

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

0 commit comments

Comments
 (0)