If secure connections to LDAP servers require client authentication, this identifies the alias of the certificate to use for client authentication when establishing a secure connection. If you set connectionSecurity, also review the trustManager and fileBasedTrustManager* settings in the security field. StartTLS means connections are secured using LDAP and StartTLS. Ssl means connections are secured using LDAPS. None (default) means connections use plain LDAP and are not secured. These files define JSON resource to LDAP entry mappings.įor details about the configuration fields, see "Mapping Configuration File". rest2ldap/endpoints/ base-path/ root-resource.json
This file defines which LDAP features the gateway uses.įor details, see "Gateway REST2LDAP Configuration File". This file defines how the gateway connects to LDAP servers, and how user identities extracted from HTTP requests map to LDAP user identities.įor details, see "Gateway Configuration File". The following list describes the configuration files, indicated by relative location under the configuration directory: config.json (gateway only) It lets you include comments in the JSON, although the JSON standard does not allow comments. The parser for REST to LDAP configuration files is lenient. In DS servers these capabilities are part of the server configuration. Only DS REST to LDAP gateway, however, has files for configuring how the gateway connects to LDAP servers, how user identities extracted from HTTP requests map to LDAP user identities, and what LDAP features the gateway uses. The format and relative locations of the mapping files are the same for DS servers and the DS REST to LDAP gateway. In a REST to LDAP gateway Servlet, the configuration files are under WEB-INF/classes. In DS server installations, the default location for the configuration files is under /path/to/opendj/config. The files for configuring the gateway and the JSON resource to LDAP entry mappings are in JSON format.
0 kommentar(er)
