Share this page
Access Rights
General access rights
|
StarTeam Server enforces access rights defined on the project/view/item level during a
clone,
push or
pull operation. In general, the user who does the first
clone on a
StarTeam project needs to be granted access rights to update the view properties. In addition, each user of the
Git client integration needs to have necessary file/folder level access rights granted to perform clone/pull or push just as
a StarTeam client user would require to checkout and check-in files. If the user is denied access to certain folder/files,
those files will not be cloned or pulled into the
Git repository. If there are any changes to the user's access rights after their clone was created, the user would have to clone
a new local
Git repository to have the new access rights take effect.
|
User account visibility
|
Git commits requires the email address of each
committer to generate unique commit hash ids.
StarTeam users require the
Administer user accounts rights to be granted in order to access other user's email addresses during
clone and
pull. If a user does not have this right granted, the email address of the
committer in
Git will be empty and could result in the commit hash ids between clones to be different. The resulting behavior is that while
each cloned repository could be pulled/ pushed to the
StarTeam Server, multiple
Git clones cannot interact with each other directly due to difference in commit graph.
|
https://admhelp.microfocus.comStarTeam8942