Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,359,862
Community Members
 
Community Events
168
Community Groups

How to restrict Crucible project access to only authors of commits on its default repository

I have setup LDAP restriction on each Crucible repository based on a group, which is already used to restrict Subversion commit thanks to a pre-commit hook.

The LDAP restriction is:

(&(objectClass=person)(sAMAccountName=${USERNAME})(memberOf=CN=prj_MyProject,OU=Projects,OU=Groups,DC=mydomain,DC=com))

Now I want to apply the same kind of restriction for project and reviews.

So I have copied agile permission scheme and have removed All logged in users from View and Create permissions to rely on the Author review role, which is supposed to look at commit author field, based on user mapping, according to

https://confluence.atlassian.com/display/CRUCIBLE/authors+in+Crucible

I expect users that have already committed into a project's default repository are allowed to view and create reviews for that project.

But it does not work. Users in group prj_MyProject can browse repository commit but have no access to the corresponding project.

I have checked users' mapping information, because Crucible and Subversion usernames does not match implicitly.

Project's fields for Default reviewers and Allowed Review Participants are blank.

How to achieve such a setup (I am used to do with JIRA projects' role and permissions scheme) ?

Is my understanding of the Author Review role wrong ?

Thank you in advance for your help

2 answers

1 accepted

0 votes
Answer accepted

Based on the answer I got from Atlassian Support, here is my current setup process to get such per-project restrictions (in additional to per-repository LDAP restriction):

  • create a group "users-X" to list project "X" users
  • create a scheme "agile-X" for each project "X", with "users-X" group in "View" and "Create" permissions

I agree it fulfills the security needs I have BUT it is really heavy to setup (compared to JIRA project roles and permission schemes for instance). I am still looking for ways to automate all that administrative work.

0 votes

PLease check the view permission in your permission schme - may be its not mapped correctly

A person who has comitted cannot view the crucible project by default - it all depends on the view permission scheme

The View permission in scheme includes "Reviewer, Creator, Author, Moderator".

The answer I got from Atlassian Support was:

  • create a group for a project users

- creat

The View permission includes "Review Roles: Reviewer, Creator, Author, Moderator".

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira

Online AMA this week: Your project management questions answered by Jira Design Lead James Rotanson

We know that great teams require amazing project management chops. It's no surprise that great teams who use Jira have strong project managers, effective workflows, and secrets that bring planning ...

172 views 1 6
Read article

Atlassian Community Events