XIldap Properties
This document describes the properties contained in the Xildap.properties file. This file is located in the WEB-INF/classes folder within the web application on the server. These properties are used by the API LdapServices class which provides methods for authentication, LDAP searches etc; this is available to API based languages such as Javascript.
|
Property |
Description |
|
Ldap.RegistryHost |
Host name or ip address of Ldap Registry server. This property is ignored if property Ldap.RegistryUrl is specified. |
|
Ldap.RegistryPort |
Port used by the Ldap Registry server. This property is ignored if property Ldap.RegistryUrl is specified. Most registries use port 389. |
|
Ldap.RegistryUrl |
Url for the Ldap Registry server. If not specified, the Url is constructed using properties Ldap.RegistryHost and Ldap.RegistryPort. |
|
Ldap.UserKeyAttributeName |
The user attribute used to search the registry for user data. This attribute should uniquely identify the user. For Active Directory, set this property to sAMAccountName. |
|
Ldap.BindDistinguishedName |
The full DN used to bind to the repository. This parameter should supply an admin userid for connections to the LDAP Registry. If not specified, Ebase will bind as 'Anonymous'. Note that anonymous binding is only supported by LDAP V3 systems and may need to be configured in the Ldap Registry. |
|
Ldap.BindPassword |
The password to be used with ldap.bindDistinguishedName |
|
Ldap.BaseDistinguishedName |
This is the DN of a directory location within the Ldap
Registry that is used as the root for all LDAP attribute searches. This will
be one or more key=value pairs separated by commas which should be specified
in reverse order of the LDAP hierarchy tree, i.e. tree root appears last. This parameter should specify the lowest point in the directory tree which is common for all userid searches e.g. if your registry contains a number of paths containing userid definitions, this parameter should specify a point in the directory that is common for all paths. The system uses subtree scope for directory searches. |
Active Directory Example:
Ldap.RegistryHost=192.168.0.123
Ldap.RegistryPort=389
#Ldap.RegistryUrl=ldap://192.168.0.123:389
Ldap.UserKeyAttributeName=sAMAccountName
Ldap.BindDistinguishedName=Admin@ebase
Ldap.BindPassword=********
Ldap.BaseDistinguishedName=OU=Ebase Users and
Groups,DC=ebasetech,DC=com