# AUTHENTICATION CONFIGURATION FOR MULTI LDAP

# WARNING !!! Before activating authentication versus multiple LDAP please be sure that EACH USER LOGIN IS UNIQUE ACROSS ALL LDAP.
# Duplicate user login across directories WILL RESULT in a single shared account in SquashTM.

# Defines the authentication provider as LDAP multi
authentication.provider=ldap-multi
# In case of multi-source authentication, use authentication.provider=ldap-multi,internal

# Defines the names of multiples LDAP separated by a comma.
# Each ldap must have is own set of properties, prefixed by the ldap name.
# You can have as many LDAP as needed, but, again, take care of duplicated username across directories.
authentication.ldap.multi.root.names=ldap1,ldap2

################ SET OF PROPERTIES FOR LDAP identified by name : ldap1 ################

# declare the ldap server url
ldap1.authentication.ldap.server.url=ldap://localhost:389

# when ldap directory cannot be accessed anonymously, configure the 'manager' user DN and password
#ldap1.authentication.ldap.server.managerDn=CN=admin,CN=Users,DC=example,DC=com
#ldap1.authentication.ldap.server.managerPassword=something

# configure a search base dn and a search query
ldap1.authentication.ldap.user.searchBase=DC=example,DC=com
ldap1.authentication.ldap.user.searchFilter=(uid={0})

# By default, connector will try to read the user's attributes (ie. ldap search) upon successful bind.
# Uncomment the following property when a user cannot read its own directory node.
#ldap1.authentication.ldap.user.fetchAttributes=false

# Advanced configuration: instead of searchBase and searchFilter, configure the base dn used for user lookup. you can specify several semi-colon separated patterns
#ldap1.authentication.ldap.user.dnPatterns=uid={0},ou=people

################ SET OF PROPERTIES FOR LDAP identified by name : ldap2 ################

# declare the ldap server url
ldap2.authentication.ldap.server.url=ldap://localhost:389

# when ldap directory cannot be accessed anonymously, configure the 'manager' user DN and password
#ldap2.authentication.ldap.server.managerDn=CN=admin,CN=Users,DC=example,DC=com
#ldap2.authentication.ldap.server.managerPassword=something

# configure a search base dn and a search query
ldap2.authentication.ldap.user.searchBase=DC=example,DC=com
ldap2.authentication.ldap.user.searchFilter=(uid={0})

# By default, connector will try to read the user's attributes (ie. ldap search) upon successful bind.
# Uncomment the following property when a user cannot read its own directory node.
#ldap2.authentication.ldap.user.fetchAttributes=false

# Advanced configuration: instead of searchBase and searchFilter, configure the base dn used for user lookup. you can specify several semi-colon separated patterns
#ldap2.authentication.ldap.user.dnPatterns=uid={0},ou=people
