The ClearCase and ClearQuest v8.0.1 Open Beta Program is now available to you. Here's the link to the website:
Feel free to download and install the beta drivers and check out the latest features. If you have a question or problem with the product please post a topic to this forum.
Client Program Manager
This topic has been locked.
4 replies Latest Post - 2012-08-15T14:14:59Z by SystemAdmin
Pinned topic ClearCase and ClearQuest v8.0.1 Open Beta Program
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-08-15T14:14:59Z at 2012-08-15T14:14:59Z by SystemAdmin
omalecot 060000JJAF344 PostsACCEPTED ANSWER
Re: ClearCase and ClearQuest v8.0.1 Open Beta Program2012-06-29T22:02:33Z in response to SystemAdminHi Brian,
I read the documentation, this is interesting, but I still have many questions.
This is about ACL. Why to introduce ACL in ClearCase ? Is it to make CC easier to use, or is CC now more complex ?
To introduce roles in ClearCase is a real improvement, but can we now - or in the near future - use VOBs without primary and secondary groups, without dependancy an windows domains ?
To add a user to a VOB : it is easy, or does it take time, do we have to reprotect all the elements with the new user ??
With ACL, is ClearCase more dependant on system versions, NFS's ones, ... ?
Re: ClearCase and ClearQuest v8.0.1 Open Beta Program2012-07-05T19:04:36Z in response to omalecotHi Olivier,
The reason we are introducing ACLs into ClearCase is because many customers found that the limitation on the number of groups to be too constraining. As a result ClearCase itself is not more or less complex, however depending on how groups are employed to implement security on elements, it could reduce the complexity of that solution. So as you say, the purpose is to augment or replace the current usage of primary and secondary groups.
However, the ClearCase implementation of ACLs does not include users. It continues to rely on the same user and operating system authorization mechanism that it has always used. There is no "new user" object,or anything like that.
ACLs does include a Role object, and you can establish permissions to ClearCase elements using the abstraction of a Role object, but ultimately that Role is then mapped to OS users and/or groups in the context of a controlled object.
There are no additional version dependencies or constraints introduced by ACLs.
I hope this answered your questions.
ClearCase Product Manager