Can Jazz Team Server be configured to use the build-in registry in IBM WebSphere Application Server (WAS), or mixed with LDAP for authentication?
The Jazz Team Server supports Tomcat and LDAP for authentication and application integration. For servers that run on IBM WebSphere, you may choose to mix LDAP and the WAS build-in repository, or just the WAS build-in repository for authentication, as there are some corporate environments that require such custom authentication mechanisms. The WAS build-in repository is categorized as "Unsupported" registry type in Jazz. When an Unsupported registry is used, the degradation is seen in the loss of the following in Jazz:
- LDAP nightly sync of user records into the Jazz repository
- The ability to import users
- The ability to display a user system roles (such as: JazzUsers, JazzAdmins) in the User Interface (UI)
- Esignature will not work
Other than the above limitations, the chance that you will run into issues within Jazz which is caused by the Unsupported user registry type is very low. However, we have not fully tested this registry type and cannot guarantee it to be 100% error free.
IBM Rational does not provide explicit support for configuring Unsupported registry with web containers. Customers would need to assume that responsibility. Rational will support the Jazz Team Server running with an Unsupported registry, given the restrictions noted above.
|Software Development||Rational Quality Manager||RQM Server||AIX, Linux, Windows||3.0.1, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 4.0, 188.8.131.52, 184.108.40.206, 4.0.1|
|Software Development||Rational Requirements Composer||Team Server||Windows, Linux, Windows, Linux||3.0.1, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 4.0, 184.108.40.206, 220.127.116.11, 4.0.1, 3.0.1, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 4.0, 220.127.116.11, 18.104.22.168, 4.0.1|