This shows you the differences between two versions of the page.
integracion_ldap [2019/11/13 08:57] montse created |
integracion_ldap [2025/03/26 07:42] (current) ale |
||
---|---|---|---|
Line 6: | Line 6: | ||
LDAP configuration is made within the application’s properties file and it can be connected to a maximum of two LDAP, that can be used as a back-up or different LDAP servers with different hierarchy and users. | LDAP configuration is made within the application’s properties file and it can be connected to a maximum of two LDAP, that can be used as a back-up or different LDAP servers with different hierarchy and users. | ||
- | Within the properties file the following keys are used: | ||
- | * sipsa.ldap.primary.base: LDAP base path in primary LDAP | ||
- | * sipsa.ldap.primary.url: Primary LDAP’s URL | ||
- | * sipsa.ldap.primary.username: Technical user DN in primary LDAP | ||
- | * sipsa.ldap.primary.password | ||
- | * sipsa.ldap.secondary.base: LDAP base path in secondary LDAP | ||
- | * sipsa.ldap.secondary.url: SecondaryLDAP’s URL | ||
- | * sipsa.ldap.secondary.username: Technical user DN in primary LDAP | ||
- | * sipsa.ldap.secondary.password: | ||
- | * sipsa.ldap.users.base: LDAP paths where users are stored in LDAP. If more tan one is required, they must be separated with@&@ | ||
- | * sipsa.ldap.users.pattern: Patterns for user’s DN. The username is represented with {0} in the DN string. If more than one is required, they must be separated with @&@. |