Skip to content

Commit de28118

Browse files
Rudy Onfroyronfroy
Rudy Onfroy
authored andcommitted
json-login-ldap
1 parent 4ea4efe commit de28118

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

reference/configuration/security.rst

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -182,7 +182,7 @@ LDAP functionality
182182
------------------
183183

184184
There are several options for connecting against an LDAP server,
185-
using the ``form_login_ldap`` and ``http_basic_ldap`` authentication
185+
using the ``form_login_ldap``, ``http_basic_ldap`` and ``json_login_ldap`` authentication
186186
providers or the ``ldap`` user provider.
187187

188188
For even more details, see :doc:`/security/ldap`.
@@ -191,8 +191,8 @@ Authentication
191191
~~~~~~~~~~~~~~
192192

193193
You can authenticate to an LDAP server using the LDAP variants of the
194-
``form_login`` and ``http_basic`` authentication providers. Simply use
195-
``form_login_ldap`` and ``http_basic_ldap``, which will attempt to
194+
``form_login``, ``http_basic`` and ``json_login`` authentication providers. Simply use
195+
``form_login_ldap``, ``http_basic_ldap`` and ``json_login_ldap``, which will attempt to
196196
``bind`` against a LDAP server instead of using password comparison.
197197

198198
Both authentication providers have the same arguments as their normal
@@ -231,8 +231,8 @@ User provider
231231

232232
Users will still be fetched from the configured user provider. If you
233233
wish to fetch your users from a LDAP server, you will need to use the
234-
``ldap`` user provider, in addition to one of the two authentication
235-
providers (``form_login_ldap`` or ``http_basic_ldap``).
234+
``ldap`` user provider, in addition to one of the three authentication
235+
providers (``form_login_ldap`` or ``http_basic_ldap`` or ``json-login-ldap``).
236236

237237
.. configuration-block::
238238

0 commit comments

Comments
 (0)