Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

Why can i create a PR with only repo READ access? Edited

I am doing some work on Bitbucket Server 6.10.1 and I'm a little confused by the personal access token permissions. I created one with Project: Read and Repo: Read access. According to the docs at https://confluence.atlassian.com/bitbucketserver/personal-access-tokens-939515499.html I was expecting that I would NOT be able to create a pull request (since this should require Repo: Write) but it looks like I am able to create one.

 

I am sending a POST to http://localhost:7990/bitbucket/rest/api/1.0/projects/PROJECT_1/repos/rep_1/pull-requests with a body

{
"title": "title",
"description": "desc",
"state": "OPEN",
"fromRef": {
"id": "refs/heads/basic_branching",
"repository": {
"slug": "rep_1",
"name": null,
"project": {
"key": "PROJECT_1"
}
}
},
"toRef": {
"id": "refs/heads/master",
"repository": {
"slug": "rep_1",
"name": null,
"project": {
"key": "PROJECT_1"
}
}
}
}

Instead of a 403, I am getting a 201 Created.

 

To sanity test the tokens themselves, I also tried testing a git push using the two different tokens. I get a

fatal: remote error: Insufficient permissions

with the repo: read access, and I get a successful push with the repo: write token. So it looks like the tokens were valid and there is some level of authorization being handled, just not where I expected.

 

Can anyone help explain what is happening? I'm using a local version for integration testing, so could there be some differences with the permission model than what is used in other versions?

1 answer

Suggest an answer

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

Calling any interview participants for Bitbucket Data Center

Hi everyone,  We are looking to learn more about development teams’ workflows and pain points, especially around DevOps, integrations, administration, scale, security, and the related challeng...

478 views 5 4
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