Inconsistent repository permission information inside CLM for a user defined in WAS (non-LDAP)
The Non-LDAP registry with WAS App Server (8.0.3) was used to configure the CLM V4.0.1 with Derby database on Windows. The five Jazz groups were created within WAS and mapped to the CCM, JTS and QM modules. A user was created with WAS under the JazzUsers group and the corresponding user was created within Jazz server. The user was added to some project areas as a project team member. However, the “Repository Permissions” within CLM is inconsistent as described below.
1) Login jts/admin and open the “Active Users”. Click the above mentioned user and view “Repository Permissions”. No group is selected for the user.
2) Login a project area (e.g. ccm/web and select the project) with the above mentioned user. Then view “View My Profile and Licenses”. Now the group for the user is selected under “Repository Permissions” as shown below.
Do you think this is a defect so that I can open a PMR to have the defect opened and fixed?
Frank |
2 answers
Ralph Schoon (63.6k●3●36●46)
| answered Jan 02 '13, 10:59 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Frank,
have you deployed the JTS and CCM on the same or on two different servers (WAS)? If you have, I would assume that you would have to configure the users and roles on both WAS or use some network deployment tricks to make sure both have the same information. Unlike with Tomcat authentication Jazz can not write to the WAS local realm, therefore you have to manage the data consistently. I would only use LDAP with WAS, because then, there would be only one place to manage the users. PS: Derby should only be used for test deployments, not for production. |
Frank,
That is expected when you are using the file based authentication with WAS Note the comment in https://jazz.net/library/article/97 If you are just testing, however, you can also configure a file based realm for application security. This realm will then be used for authentication and authorization, but Jazz will not be able to query what roles a user has or import users. Comments 1
This behavior is also mentioned in Repository permissions for a user in web UI is not always accurate (231533).
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.