-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(bitbucket-server): Add bitbucket http access token support #28093
feat(bitbucket-server): Add bitbucket http access token support #28093
Conversation
Is there still a use case for keeping username+token or could it be deprecated in a future release and support token only? |
At least from a performance perspective, with "token-only" in bitbucket-server, renovate fetches the entire list of PRs as it cannot filter by author. It might make sense to try out if automerge works with token-only or, if not, highlight this in the docs. According to BB docs:
|
In that case we should either:
Great catch! |
This would make the whole PR obsolete. The problem is that you can create access tokens on project/repo level. Those tokens don't have a user.
|
Do tokens exist with or without username, or only without username? |
You can create user based access tokens and repository/project based tokens without user. Project/Repository tokens only work with Bearer since they don't have a user |
My question was a little ambiguous, so I need to ask a different way: Is it possible to combine tokens with username, or are they always without username? |
|
We decide which auth to use, not the user. It's not answering my question |
There are tokens with and without usernames
There are tokens with username and tokens without username |
Co-authored-by: Michael Kriese <[email protected]>
🎉 This PR is included in version 37.288.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Changes
Add the possibility to use HTTP access tokens for authentication against Bitbucket Server. Personal access tokens as well as porject/repository scoped tokens will work. When setting a token
Bearer Auth
will be used instead ofBasic Auth
(Ref: Using HTTP access tokensContext
fixes #14900
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: