This shows you the differences between two versions of the page.
es:integracion_ldap [2018/01/23 14:09] tast |
es:integracion_ldap [2025/03/26 08:39] (current) ale |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== Integración LDAP ===== | + | ====== Integración LDAP ====== |
- | {{:TAST-icon.png?nolink&70|}} TAST is connected to LDAP for the processes of authentication and authorization. | + | TAST está conectado a LDAP para los procesos de autenticación y autorización. |
- | ===== 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. | + | ===== Configuración ===== |
- | 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 @&@. | + | |
+ | La configuración LDAP se realiza dentro del archivo de propiedades de la aplicación y se puede conectar a un máximo de dos LDAP, que se pueden utilizar como servidores de respaldo o como servidores diferentes LDAP, con diferentes jerarquías y usuarios. |