branch level permissions

[James Ching]

I'm testing the branch level permissions in Stash 2.0 but I must be missing something... I'm having trouble getting it to work, here's the setup:

Security Setup for 'testuser'

- Project Level Permissions: Observer

- Repository Branch Level Security: Write (Just to the available branch options, I tried the advanced as well with no luck)

Everytime I try to push the branch, i get:

fatal: remote error: Insufficient permissions

You do not have permission to push to the repository test in project

fatal: The remote end hung up unexpectedly

The 'testuser' can only write to the repository if I set it to Contributor at Project Level but then it can write to all branches. Am I missing a setting somewhere?

Thanks for any hints!

[jhinch (Atlassian) · Accepted solution]

Just to clarify branch permissions doesn't elevate the project level permissions it is more of a restriction. When you push changes to a repository first the project level permission is checked. This is the same as it was in Stash 1.x meaning the user must be a contributor (have write access) to the project in order for their push to proceed. Stash then checks the branch permissions for each branch which is being updated. If a restriction exists and the user doesn't have permission the push is rejected. If there is no restriction or they have permission the push is successful.

[bswift]

Hey Jason,

I posted this today:

https://answers.atlassian.com/questions/134904/stash-security-bug-branch-permissions

It appears that your comment about branch level permissions being more restrictive is not functioning for us in Stash 2.0.

[Ulrich Kuhnhardt]

Assuming the contributor that does not have push access to master but has push access to contrib then the contributor should make sure to only work, commit and push on branch contrib

[James Ching]

Ah sorry, after some testing, ALL users need to be setup with contributor access and you have to assign permissions to the master branch (cannot leave blank).