Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-7735

Allow HTTP access to repositories via OAuth (BB-8891)

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Github now provides OAuth tokens as an authentication mechanism for pulling/cloning repositories. Do you have a plan/timeline for implementing this?

      Currently, the only way to deploy private repositories onto platforms like Heroku (that don't allow private SSH keys) is to explicitly use username/password credentials, which aren't easily revokable and pollute logs & source control with credentials (which is bad!).

            [BCLOUD-7735] Allow HTTP access to repositories via OAuth (BB-8891)

            Thank you, @erikvanzijst. Now we can hook up our internal CI system. One question, though: do I need a token pair for the Team account to see the team's private repositories? It appears I can only see the public repositories (including my own) with the token pair. I don't see an option to enable that in the token configuration.

            seanerussell added a comment - Thank you, @erikvanzijst. Now we can hook up our internal CI system. One question, though: do I need a token pair for the Team account to see the team's private repositories? It appears I can only see the public repositories (including my own) with the token pair. I don't see an option to enable that in the token configuration.

            evzijst added a comment -

            We recently introduced OAuth 2 and also added the ability to use them as HTTP Basic Auth credentials.

            evzijst added a comment - We recently introduced OAuth 2 and also added the ability to use them as HTTP Basic Auth credentials .

            @sirvon Thanks. That worked!

            phuongnd08 added a comment - @sirvon Thanks. That worked!

            sirvon added a comment -

            sirvon added a comment - @phuongnd08 https://bitbucket.org/site/master/issue/10182/access-tokens-for-command-line-use

            How to get team token?

            phuongnd08 added a comment - How to get team token?

            Bummer. Time to migrate to github.

            seanerussell added a comment - Bummer. Time to migrate to github.

            tiagobrito added a comment -

            OMG this isn't implemented yet? And still no clear answer on how to achieve this...

            tiagobrito added a comment - OMG this isn't implemented yet? And still no clear answer on how to achieve this...

            From where does the the token generated for raw urls in private repo? It is different for every urls. So I suppose it doesn't have anything to do with oauth token. Does it?

            Legacy Bitbucket Cloud User (Inactive) added a comment - From where does the the token generated for raw urls in private repo? It is different for every urls. So I suppose it doesn't have anything to do with oauth token. Does it?

            No, you can use that token only for team accounts.
            You cannot use that to access the repositories, Bitbucket doesn't support OAuth 2.0 protocoll.

            If you want to do that you have to explicitly use username/password or use the SSH protocoll with RSA keys.

            Gábor Domonkos added a comment - No, you can use that token only for team accounts. You cannot use that to access the repositories, Bitbucket doesn't support OAuth 2.0 protocoll. If you want to do that you have to explicitly use username/password or use the SSH protocoll with RSA keys.

            I tried @yamadapc method but it failed.

            Steps:
            -I loged in with bitbucket omniauth and saved the token
            -I used that saved token to clone a repo.
            -I got this: fatal: Authentication failed for 'https://A8E3AFxm3QJrYtarZB

            orbanbotond added a comment - I tried @yamadapc method but it failed. Steps: -I loged in with bitbucket omniauth and saved the token -I used that saved token to clone a repo. -I got this: fatal: Authentication failed for ' https://A8E3AFxm3QJrYtarZB

              Unassigned Unassigned
              legacy-bitbucket-user Legacy Bitbucket Cloud User (Inactive)
              Votes:
              15 Vote for this issue
              Watchers:
              21 Start watching this issue

                Created:
                Updated:
                Resolved: