Role Mapping
Kevin Creason (11●2●3)
| asked Jan 23 '17, 6:05 p.m.
retagged Jan 30 '17, 10:36 a.m. by Michael Afshar (701●4) I'm building up Jazz Team Server 6.0.3 for users in our organization. Apologies, I don't quite understand all the names of the products to check off -- but it is DOORS next Gen, Jazz Team Server, with some modules for quality management, and it installs under the "clm" in the directory tree on the linux server.
<!-- Allows requests to j_security_check to be checked for a CSRF attack. Before the closing servlet tag, I have added my security-role-ref: <!-- Added for Cams SSO roles from the AD --> <security-role-ref> <role-name>JazzUsers</role-name> <role-link>JS-DLG-ISS-SSO_JazzUsers</role-link> </security-role-ref> <security-role-ref> <role-name>JazzAdmins</role-name> <role-link>JS-DLG-ISS-SSO_JazzAdmins</role-link> </security-role-ref> <security-role-ref> <role-name>JazzGuests</role-name> <role-link>JS-DLG-ISS-SSO_JazzGuests</role-link> </security-role-ref> <security-role-ref> <role-name>JazzProjectAdmins</role-name> <role-link>JS-DLG-ISS-SSO_JazzProjectAdmins</role-link> </security-role-ref> Then, down in the security-contstraint section, I added the new roles names: <auth-constraint> <role-name>JazzUsers</role-name> <role-name>JazzAdmins</role-name> <role-name>JazzGuests</role-name> <role-name>JazzProjectAdmins</role-name>
<role-name>JS-DLG-ISS-SSO_JazzUsers</role-name> <role-name>JS-DLG-ISS-SSO_JazzAdmins</role-name> <role-name>JS-DLG-ISS-SSO_JazzGuests</role-name> <role-name>JS-DLG-ISS-SSO_JazzProjectAdmins</role-name> </auth-constraint> Then lower down, I'm basically just searching for JazzAdmins in order to find the locations to modify, I add in the new names underneath the existing role names. This is in a block following login-config: <security-role> <role-name>JazzAdmins</role-name> </security-role> <security-role> <role-name>JazzUsers</role-name> </security-role>
<role-name>JazzGuests</role-name> </security-role>
<role-name>JazzProjectAdmins</role-name> </security-role>
<role-name>JazzDebug</role-name> </security-role>
<security-role> <role-name>JS-DLG-ISS-SSO_JazzAdmins</role-name> </security-role> <security-role> <role-name>JS-DLG-ISS-SSO_JazzUsers</role-name> </security-role>
<role-name>JS-DLG-ISS-SSO_JazzGuests</role-name> </security-role>
<role-name>JS-DLG-ISS-SSO_JazzProjectAdmins</role-name> </security-role> What have I missed, or what have I messed up? |
One answer
It seems that you have made things too complicated. CLM provides its own SSO solutions and you should understand what if offers before trying to implement your own. The first question will be, what you try to SSO with?
Comments Thank you, the role-mapping is the issue. I had explored those SSO options and ruled them out for a variety of reasons. Utilizing the servlet filter should work and would be the most flexible and supportable method for me.
Donald Nong
commented Jan 25 '17, 12:50 a.m.
The role names are hard coded in the applications, so if you add new roles/groups (as in the servlet), they will not get recognized. The application.xml file is for Liberty to convert/map the group name(s) from LDAP or other user repository to the appropriate roles (JazzAdmins and etc).
|
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.