en:ldap_integration
Differences
This shows you the differences between two versions of the page.
|
en:ldap_integration [2018/01/23 10:37] tast |
— (current) | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== LDAP Integration ===== | ||
| - | |||
| - | {{:TAST-icon.png?nolink&70|}} TAST is connected to LDAP for the processes of authentication and authorization. | ||
| - | |||
| - | ==== Configuration ==== | ||
| - | |||
| - | 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 @&@ | ||
| - | |||
| - | |||
en/ldap_integration.1516703872.txt.gz · Last modified: 2018/01/23 10:37 by tast
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 3.0 Unported
