@salmon-lock-64866 fyi I have a PR here https://github.com/OpenHands/OpenHands/pull/12825 to authenticate with bitbucket data center as an identity provider for enterprise. There are still some things to iron out with the login flow but I'm thinking after that the next step would be incorporating and testing the bitbucket integration PR changes. I will be out for a week but my team will be continuing to work on this

@able-napkin-92802 ^^^^

@dry-book-58714 Thanks for the link! I realize after reviewing I don't have my test instance at point I'm ready for oauth2 (converting to HTTPS for example). I'll need a bit more time to get that resolved and then I'll test this out.

https://github.com/OpenHands/OpenHands/pull/12389 - isn't this adding Bitbucket auth via API Tokens instead of App Passwords?

@able-napkin-92802 BitBucket Thread for your awareness...

Thanks @curved-angle-80449. I've picked up where @dry-book-58714 left off on ironing out the OAuth signin flow for enterprise. I'll be taking a closer look at the other PRs referenced in this thread today.

I am still not aligned with the output here - which is the PR when merged that gives me the ability to use Bitbucket Cloud API Token authentication in the open source version of OpenHands?

I think you're right, it should be 12389 - does it work for you if you run on the branch?

I am currently using the docker image

<http://docker.openhands.dev/openhands/openhands:main|docker.openhands.dev/openhands/openhands:main>

can I just replace the

main

with

bnainar:feat(bitbucket)--api-tokens

and expect it to work?

Yes, if that is the image in the PR description

I don't see any image in the PR description

One PR addresses cloud tokens specifically. The other PR adds bitbucket server support but also mostly solves cloud token issues as well. It is missing fact the username and token should be escaped though which both cloud and server need.

this is still open?

Its a timely question since the PR for Bitbucket Data Center support in OSS was just merged. The PR went in a bit different direction and broke out Bitbucket DC into its own provider so Cloud stayed closer to original design. So I went back and reviewed current Bitbucket Cloud logic. It appears to me that you should be able to use Bitbucket Cloud authentication tokens with the Bitbucket integration successfully but if you then try to clone a git repo its likely to fail because the token is still not correctly URL encoded when creating the authenticated git URL (Bitbucket Data Center is correctly encoded). If you want to test it, fill in with "token" and not "username:token" in the settings screen. I do not have a Cloud account to test myself. Assuming my code review is correct, think the remaining logic is only 5 lines or so required for git URL.