By default, the Jazz™ Team Server stores the user information with encrypted passwords in the user database.
If you plan to use an LDAP registry with your Jazz Team Server, you must configure your Apache Tomcat or WebSphere® Application Server to use an LDAP registry to authenticate users.
| Parameter | Value description |
|---|---|
| LDAP Registry Location | The URL that references your LDAP server. ldap://ldap.example.com:389 |
| User Name | The user name to log in to this LDAP server. Some LDAP servers do not require a login and password. In this case, this parameter is blank. |
| Password | The password associated with the user name. |
| Base User DN | The search base indicates where in the hierarchy to begin the search for the users. For example, "o=[company],l=[your city],c=[your country]" |
| User Property Names Mapping | The mapping of Jazz user property names to LDAP registry
entry attribute names. You must define the following mappings:
|
| Base Group DN | This search base indicates where in the hierarchy to begin the search the group names, for example, ou=memberlist,ou=yourgroups,o=example.com |
| Jazz to LDAP Group Mapping | The mapping between Jazz groups and LDAP groups. One Jazz group can
be mapped to multiple LDAP groups. The LDAP groups must be separated by a
semicolon. For example, JazzAdmins=LDAPAdmins1;LDAPAdmins2 maps JazzAdmins
group to LDAPAdmins1 and LDAPAdmins2. Jazz Team
Server defines 4 groups to map with:
|
| Group Name Property | The LDAP Property that represents the name of the Jazz groups in the LDAP registry. For example, cn. |
| Group Member Property | The LDAP Property that represent the members of a group in the LDAP registry. For example, uniquemember. |
Did this help? You can provide feedback at Jazz.net (registration required): Comment in the forums or submit a bug