Skip to content

Clarification on search user #9307

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

Merged
merged 2 commits into from
May 28, 2018
Merged

Clarification on search user #9307

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f08eab2
Clarification on search user
brooksvb Feb 21, 2018
b7a2009
Minor reword
javiereguiluz May 28, 2018
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
10 changes: 10 additions & 0 deletions security/ldap.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -173,6 +173,16 @@ use the ``ldap`` user provider.
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::

It's important to note that the user you configure for the user provider
is only going to be retrieving data. It is a statically defined user and
password. If you wish to keep your password out of version control, you
may want to configure the password as a parameter.

If your ldap server allows you to retrieve information anonymously, you
can leave the ``search_dn`` and ``search_password`` as ``null``.

The ``ldap`` user provider supports many different configuration options:

Expand Down