As touched upon in
Scenarios for Mapping Multiple Repositories to a Single Stream, one of the advantages of using
GitCentric in a
Git environment is that you can use both
GitCentric and
AccuRev security features to control access to files, a feature not natively provided by
Git.
GitCentric makes use of two kinds of Access Control Lists (ACLs):
- GitCentric “group-based” ACLs, which define access to
Git repositories.
- AccuRev Element ACLs, which define permissions on the
AccuRev Server down to the individual element level.
Using these two types of ACLs, you can approach
GitCentric security in two ways:
- Using
GitCentric group-based ACLs to specify allow and deny privileges on a repository (“project”) basis.
- Mapping multiple repos as different “views” on
AccuRev-controlled elements. The
AccuRev-controlled elements may optionally be secured with
AccuRev Element ACLs (EACLs).