Skip to content
Merged
Changes from all commits
Commits
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
9 changes: 6 additions & 3 deletions install_config/configuring_authentication.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -479,11 +479,9 @@ to create a search filter that looks like:

For example, consider a URL of:

====
----
ldap://ldap.example.com/o=Acme?cn?sub?(enabled=true)
----
====

When a client attempts to connect using a user name of `bob`, the resulting
search filter will be `(&(enabled=true)(cn=bob))`.
Expand All @@ -494,7 +492,6 @@ If the LDAP directory requires authentication to search, specify a `bindDN` and
[[ldap-example-config]]

.Master Configuration Using *LDAPPasswordIdentityProvider*
====
----
oauthConfig:
...
Expand Down Expand Up @@ -550,6 +547,12 @@ configured URL. If empty, system trusted roots are used. Only applies if
`ldaps://` URLs connect using TLS, and `ldap://` URLs are upgraded to TLS.
<13> An RFC 2255 URL which specifies the LDAP host and search parameters to use,
xref:ldap-url[as described above].

[NOTE]
====
To whitelist users for an LDAP integration, use the `lookup` mapping method.
Before a login from LDAP would be allowed, a cluster administrator must create
an identity and user object for each LDAP user.
====

[[BasicAuthPasswordIdentityProvider]]
Expand Down