It's all about the answers!

Ask a question

How to avoid role inheritance from RTC project area to its team area level

Maheswari Karuppiah (826) | asked Jun 08 '18, 2:47 a.m.
edited Jun 08 '18, 7:16 a.m. by Ralph Schoon (63.3k33646)

 1. Get members from the project area

curl -k -u %USER%:%PASSWORD% -o "proj_%%a.xml" -H "Accept: application/xml" !P_URL!/members
2. Role remapped
3. Delete members from the project area
curl -D - -k -u %USER%:%PASSWORD% -X DELETE !P_URL!/members
4. Get members from the team area
curl -k -u %USER%:%PASSWORD% -o "team_%%i.xml" -H "Accept: application/xml" !T_URL!/members

The output xml file from Step 4 is giving all the roles inherited from Project area.

Pls let us know how to avoid this role inheritance

One answer

permanent link
Karthik Krishnan (8845119163) | answered Jun 08 '18, 8:03 a.m.

Not sure what your use case is but you can break the inheritance in each and every team area by adapting changes accordingly.

Maheswari Karuppiah commented Jun 08 '18, 8:10 a.m.

 We are trying to change the existing roles to new roles for all project areas and the respective team areas. While doing this with the script we are facing this inheritance problem which we want to avoid. 

Manual change is possible, but while trying with the script it is fetching the roles from the parent and adding it to the team area level. It is inheriting on run time.

Karthik Krishnan commented Jun 08 '18, 8:54 a.m. | edited Jun 08 '18, 9:00 a.m.
Wait! now I get it. You are manipulating the users and not the role permissions itself. Right?
My bad.

What i know is first remove all the roles and then update the new roles. This worked via RTC Java API.  Do you use that ?

Maheswari Karuppiah commented Jun 11 '18, 2:52 a.m.

 I didnt try with Java API. Do you have one or it is already available. Pls share. I'll try to implement

Karthik Krishnan commented Jun 11 '18, 4:34 a.m.

Sorry I don't have it with me as it was in my older job.

Your answer

Register or to post 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.