Concept of RTC Access Rights
Hi,
I'm looking at the access controls of RTC and found there are several types.
1. CAL (Build System, Clearcase Synchronizer, ClearQuest Synchronizer, Contributor, Dev, Dev for IBM Ent Platforms, Stakeholder)
2. Repository Permissions (JazzAdmins, JazzDWAdmins, JazzGuests, JazzUsers, JazzProjectAdmins)
3. Team Artifacts>Project Area's Project role permissioning and team role permissioning
4. Team Organization>Team Area's role permissioning
I realise that I still have not grasped the concepts completely. Eg, what is the purpose of having each of these type of access control, how are they related, why do we need a separate Build System CAL etc.
Would be grateful if someone can shed some light here.
Thanks & Regards,
Swat
I'm looking at the access controls of RTC and found there are several types.
1. CAL (Build System, Clearcase Synchronizer, ClearQuest Synchronizer, Contributor, Dev, Dev for IBM Ent Platforms, Stakeholder)
2. Repository Permissions (JazzAdmins, JazzDWAdmins, JazzGuests, JazzUsers, JazzProjectAdmins)
3. Team Artifacts>Project Area's Project role permissioning and team role permissioning
4. Team Organization>Team Area's role permissioning
I realise that I still have not grasped the concepts completely. Eg, what is the purpose of having each of these type of access control, how are they related, why do we need a separate Build System CAL etc.
Would be grateful if someone can shed some light here.
Thanks & Regards,
Swat
3 answers
1. CAL: This is a licensing question. You are constrained by what you
have paid for.
2. I'll defer this until after I've discussed 3 and 4.
3. This is how you control access to all objects owned by the project area.
4. This is how you override the process for a specific team area within
a project area. So this is just a way of adjusting the permissions
defined by 3.
2. There are objects that do not belong to a project area (and so are
not controlled by 3 and 4 permissions). This is also how you control
permissions for who can create new project areas, and how you make sure
a project area does not get isolated with nobody able to update it.
Cheers,
Geoff
On 2/6/2011 12:23 AM, swatoon wrote:
have paid for.
2. I'll defer this until after I've discussed 3 and 4.
3. This is how you control access to all objects owned by the project area.
4. This is how you override the process for a specific team area within
a project area. So this is just a way of adjusting the permissions
defined by 3.
2. There are objects that do not belong to a project area (and so are
not controlled by 3 and 4 permissions). This is also how you control
permissions for who can create new project areas, and how you make sure
a project area does not get isolated with nobody able to update it.
Cheers,
Geoff
On 2/6/2011 12:23 AM, swatoon wrote:
Hi,
I'm looking at the access controls of RTC and found there are several
types.
1. CAL (Build System, Clearcase Synchronizer, ClearQuest
Synchronizer, Contributor, Dev, Dev for IBM Ent Platforms,
Stakeholder)
2. Repository Permissions (JazzAdmins, JazzDWAdmins, JazzGuests,
JazzUsers, JazzProjectAdmins)
3. Team Artifacts>Project Area's Project role permissioning and
team role permissioning
4. Team Organization>Team Area's role permissioning
I realise that I still have not grasped the concepts completely. Eg,
what is the purpose of having each of these type of access control,
how are they related, why do we need a separate Build System CAL
etc.
Would be grateful if someone can shed some light here.
Thanks& Regards,
Swat
Geoffrey Clemm <geoffrey> writes:
Hello Geoff,
Is the answer for #1 really this simple? RTC 2.x has Contributor and
Developer licenses. By giving a user a Contributor license, one can
effectively limit access to the SCM to read-only. The "Source Control"
folder, in the rich client, is not present in the Team Artifacts view
for users with a Contributor license.
In RTC 3.0 a Stakeholder license was added which gives read and write
access to Change Management and read access to Reports. 3.0's addition
of a license seems be of a greater scope than merely what was paid for.
Am I reading too much into the licensing tech article?
http://jazz.net/library/article/548/
Thank you,
-Garrett Rolfs
Hello Geoff,
1. CAL: This is a licensing question. You are constrained by what you
have paid for.
Is the answer for #1 really this simple? RTC 2.x has Contributor and
Developer licenses. By giving a user a Contributor license, one can
effectively limit access to the SCM to read-only. The "Source Control"
folder, in the rich client, is not present in the Team Artifacts view
for users with a Contributor license.
In RTC 3.0 a Stakeholder license was added which gives read and write
access to Change Management and read access to Reports. 3.0's addition
of a license seems be of a greater scope than merely what was paid for.
Am I reading too much into the licensing tech article?
http://jazz.net/library/article/548/
Thank you,
-Garrett Rolfs
I believe all of the statements below are consistent with the statement
"you are constrained by what you have paid for", i.e., these are
constraints based on what kind of license you have bought, rather than
constraints based on what your process allows. What in particular in
article 548 led you to believe otherwise?
Cheers,
Geoff
On 2/8/2011 4:52 PM, Garrett Rolfs wrote:
"you are constrained by what you have paid for", i.e., these are
constraints based on what kind of license you have bought, rather than
constraints based on what your process allows. What in particular in
article 548 led you to believe otherwise?
Cheers,
Geoff
On 2/8/2011 4:52 PM, Garrett Rolfs wrote:
Geoffrey Clemm<geoffrey> writes:
Hello Geoff,
1. CAL: This is a licensing question. You are constrained by what you
have paid for.
Is the answer for #1 really this simple? RTC 2.x has Contributor and
Developer licenses. By giving a user a Contributor license, one can
effectively limit access to the SCM to read-only. The "Source Control"
folder, in the rich client, is not present in the Team Artifacts view
for users with a Contributor license.
In RTC 3.0 a Stakeholder license was added which gives read and write
access to Change Management and read access to Reports. 3.0's addition
of a license seems be of a greater scope than merely what was paid for.
Am I reading too much into the licensing tech article?
http://jazz.net/library/article/548/
Thank you,
-Garrett Rolfs