It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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.

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
Community showcase
Published in Opsgenie

Two Chances to Improve your Incident Management Workflow

Hi there!  We all know that incidents can be messy, but they happen. Managing your response and planning ahead can make a *huge* difference in the duration and chaos of an incident. We have ...

134 views 0 2
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you