I have a Stash user authenticating via AD who has write access to a project and is unable to push to a specific repository. He's able to push to repositories in other projects. SSH is setup correctly; cloning is fine, but pushing results in fatal: remote error: Insufficient permissions
You do not have permission to push to the repository retailpaymentservices in
project Fully Governed Enterprise Services
fatal: Could not read from remote repository.
Ok, that eliminates one potential issue.
I've just checked the code paths and that error message is written when
So, I'd double check the permissions on the project in question and the user's group memberships to make sure it's all set up correctly.
From earlier answers it sounds like you've already double-checked this. Assuming everything is set up correctly and it's still not working, it might be a bug. Perhaps https://jira.atlassian.com/browse/CWD-3796?Do you have multiple User directories set up for Stash?
- Are the write permissions given to a group that the user should belong to, but actually does not? (You can check the group memberships if you open the user's details in Administration/Users on the web interface.)
- It is possible that some branch permissions setting prevents the user from pushing to the branch they were trying to push to. (Repo's page -> Settings/Branch permissions)
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs