When trying to use OAuth 2 authentication process it fails with error code 400 and the following message:

      Client credentials missing; this request needs to be authenticated with the OAuth client id and secret

      I am sending my request exactly as the RFC says. I took my github implementation and changed the Authorization Url and Access Token Url.
      I am passing Client ID and
      Client Secret correctly and
      setting Content-Type: ''application/x-www-form-urlencoded"

      I am being redirected to log-in page at bit-bucket but then when i perform the access_token request i get this error!

      This is not working!

            [BCLOUD-11520] OAuth 2 authentication does not work.

            Attachment 2170067394-ian_buchanan__edit_oauth_consumer%E2%80%94_Bitbucket.png has been added with description: Originally embedded in Bitbucket issue #11520 in site/master

            devpartisan added a comment - Attachment 2170067394-ian_buchanan__ edit_oauth_consumer %E2%80%94_Bitbucket.png has been added with description: Originally embedded in Bitbucket issue #11520 in site/master

            Attachment 2910085813-Screen%20Shot%202015-07-16%20at%2011.27.08%20am.png has been added with description: Originally embedded in Bitbucket issue #11520 in site/master

            srutiharikumar added a comment - Attachment 2910085813-Screen%20Shot%202015-07-16%20at%2011.27.08%20am.png has been added with description: Originally embedded in Bitbucket issue #11520 in site/master

            Attachment 3081865222-Screen%20Shot%202015-07-16%20at%2011.27.02%20am.png has been added with description: Originally embedded in Bitbucket issue #11520 in site/master

            srutiharikumar added a comment - Attachment 3081865222-Screen%20Shot%202015-07-16%20at%2011.27.02%20am.png has been added with description: Originally embedded in Bitbucket issue #11520 in site/master

            Attachment 2229087237-Screen%20Shot%202015-07-16%20at%2011.26.50%20am.png has been added with description: Originally embedded in Bitbucket issue #11520 in site/master

            srutiharikumar added a comment - Attachment 2229087237-Screen%20Shot%202015-07-16%20at%2011.26.50%20am.png has been added with description: Originally embedded in Bitbucket issue #11520 in site/master

            Attachment 975456083-Screen%20Shot%202015-07-16%20at%2011.26.30%20am.png has been added with description: Originally embedded in Bitbucket issue #11520 in site/master

            srutiharikumar added a comment - Attachment 975456083-Screen%20Shot%202015-07-16%20at%2011.26.30%20am.png has been added with description: Originally embedded in Bitbucket issue #11520 in site/master

            Attachment Screen Shot 2015-07-02 at 5.07.31 PM.png has been added with description: Originally attached to Bitbucket issue #11520 in site/master

            Legacy Bitbucket Cloud User (Inactive) added a comment - Attachment Screen Shot 2015-07-02 at 5.07.31 PM.png has been added with description: Originally attached to Bitbucket issue #11520 in site/master

            Attachment Screen Shot 2015-07-02 at 5.07.55 PM.png has been added with description: Originally attached to Bitbucket issue #11520 in site/master

            Legacy Bitbucket Cloud User (Inactive) added a comment - Attachment Screen Shot 2015-07-02 at 5.07.55 PM.png has been added with description: Originally attached to Bitbucket issue #11520 in site/master

            I agree with Jim, needed to dissect all the info in this page to make OAuth work. Best to update the documentation.

            Nico Mommaerts added a comment - I agree with Jim, needed to dissect all the info in this page to make OAuth work. Best to update the documentation.

            I hit this issue today as well. More than a year later. Lucky for me this issue existed. I would've never figured out I had to add a bogus callback url. Like Ryne Everett said, there should be a default one.

            TheRealJimbo added a comment - I hit this issue today as well. More than a year later. Lucky for me this issue existed. I would've never figured out I had to add a bogus callback url. Like Ryne Everett said, there should be a default one.

            I'm seeing the following error:

            {"error_description": "Requests must be authenticated using OAuth client credentials", "error": "unauthorized_client"}
            

            What could be wrong?

            matthewcheok added a comment - I'm seeing the following error: { "error_description" : "Requests must be authenticated using OAuth client credentials" , "error" : "unauthorized_client" } What could be wrong?

              Unassigned Unassigned
              legacy-bitbucket-user Legacy Bitbucket Cloud User (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: