Security on Components
We have been looking into using the source code management within RTC and were wondering whether anyone has done security at the component level?
We have a number of people in our repository that shouldnt be able to view the code and some areas of the code that we would like to secure to only allow certain members of the team to view and edit. At the moment the only way we can see this working is by using separate project areas for the code and work items. Which feels abit unnatural?
Has any one any thoughts on this of how we might be able to do it?
Thanks
Adam
We have a number of people in our repository that shouldnt be able to view the code and some areas of the code that we would like to secure to only allow certain members of the team to view and edit. At the moment the only way we can see this working is by using separate project areas for the code and work items. Which feels abit unnatural?
Has any one any thoughts on this of how we might be able to do it?
Thanks
Adam
One answer
Currently read protection is supported at the project level and applies to Source Control components. This means that you will have to use a separate project area to control membership lists for access control. However, you can mix and match streams with public and private components.
The following blog entry and video outline the current options.
http://jazz.net/blog/index.php/2009/05/21/patterns-for-read-protecting-source-code-2/
Cheers,
Jean-Michel
The following blog entry and video outline the current options.
http://jazz.net/blog/index.php/2009/05/21/patterns-for-read-protecting-source-code-2/
Cheers,
Jean-Michel