TAST tool Menu
TAST Adaptors
Adaptors examples
TAST Integrations
Interesting features
Documentation of technical administration
Modeling recommendations
Training in the TAST tool
TAST tool Menu
TAST Adaptors
Adaptors examples
TAST Integrations
Interesting features
Documentation of technical administration
Modeling recommendations
Training in the TAST tool
This is an old revision of the document!
TAST is connected to LDAP for the processes of authentication and authorization.
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 @&@