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:
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
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
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):
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.
Calling all Confluence Cloud Admins! We created a new Community Group to support your unique needs as Confluence admins. This is a group where you can ask questions, access resou...
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