![]() |
Telelogic SYNERGY (steve huntington) | ![]() |
Topic Title: Can't figure out how to assign group security to existing objects Topic Summary: Looking for help in the use of group security Created On: 16-Nov-2007 17:40 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I understand that group security can be used to restrict access to objects in Synergy/CM. I was able to create two groups. For all of our existing objects, we would like to secure them to just one of these groups.
I found very little in the documentation about how to use group security. My limited understanding leads me to think that I need to first run a query like; ccm query "has_attr('groups') and has_attr('source')" I tried this and it returned nothing. Would this mean that none of our objects have the "groups" attribute? I just don't know where to go with this. Provided my query did return results, I am thinking that I would then set the value of the "groups" attribute to the appropriate group name on the entire results set. This is pretty much a guess on my part. Going about setting security on new objects then presents another challenge. Doing it via a trigger has been mentioned to me. Another thing for me to find out about. But for right now, if anyone can answer my question about how to establish group security on our existing objects, I would be most appreciative. |
|
![]() |
|
![]() |
|
Doug,
First query for the objects that you wish to modify. These might all be in the same project or project hierarchy, or perhaps files under some directory in a project. Just use normal ccm query syntax to get the objects you want. Query expression syntax is described in the CLI help. Next, make sure that you are in group_mgr role in the Classic Client. You can then use the ccm groups -assign command using "@" as the argument, meaning the query selection set. This is described in the CLI help. The reason why you need the group_mgr role is that this role is required when changing the group security of an object that is not the root history version of an object. This prevents someone who has check out access from hijacking the security without a group manager's permission. Regards, David. |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.