libre.sh/keycloak-scim
3
0
Fork 0
Code Issues 15 Pull requests Releases Packages Activity Actions

Update topics/user-federation/ldap.adoc

Browse source
This commit is contained in:
Stian Thorgersen 2016-06-10 09:04:57 +02:00
parent 8c28a3467f
commit a9512e5a32
1 changed files with 1 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
topics/user-federation/ldap.adoc
View file

@ -54,8 +54,7 @@ Other options::
When you configure a secured connection URL to your LDAP store(for example `ldaps://myhost.com:636` ), When you configure a secured connection URL to your LDAP store(for example `ldaps://myhost.com:636` ),
{{book.project.name}} will use SSL for the communication with LDAP server. {{book.project.name}} will use SSL for the communication with LDAP server.
The important thing is to properly configure a truststore on the {{book.project.name}} server side, because SSL won't work The important thing is to properly configure a truststore on the {{book.project.name}} server side, otherwise {{book.project.name}} can't trust the SSL connection to LDAP.
if {{book.project.name}} can't trust the SSL connection with LDAP ({{book.project.name}}.
The global truststore for the {{book.project.name}} can be configured with the Truststore SPI. Please check out the link:{{book.installguide.link}}[{{book.installguide.name}}] for more detail. The global truststore for the {{book.project.name}} can be configured with the Truststore SPI. Please check out the link:{{book.installguide.link}}[{{book.installguide.name}}] for more detail.
If you don't configure the truststore SPI, the truststore will fallback to the default mechanism provided by Java (either the file provided by system property `javax.net.ssl.trustStore` If you don't configure the truststore SPI, the truststore will fallback to the default mechanism provided by Java (either the file provided by system property `javax.net.ssl.trustStore`