Page MenuHomePhabricator

Auth provider for Bitbucket
Closed, ResolvedPublic

Description

I took a stab at this a while ago, but didn't get very far towards anything working - it's OAuth1, yet seems to be rather different from both JIRA and Twitter.

Event Timeline

asherkin raised the priority of this task from to Needs Triage.
asherkin updated the task description. (Show Details)
asherkin added a project: Auth.
asherkin added a subscriber: asherkin.

It looks at least somewhat similar to Twitter to me, at least at first glance. We have more reasonable OAuth1 primitives now than we did in the past, so this might not be too difficult.

epriestley triaged this task as Wishlist priority.Dec 22 2013, 4:42 PM

Hrrm, I can't get this working either. It looks like Twitter OAuth, and the first step of the handshake works fine, but then token verification fails abruptly with no useful information ("HTTP 400 Could not verify OAuth request.").

The documentation doesn't provide enough values (e.g., example Consumer Secret) to easily bisect the problem. The documentation doesn't mention any of the HTTP headers so I tried shipping the whole workflow over normal POST parameters, but wasn't successful. The first step of the handshake also works fine, which implies the request is being understood.

Here's how far I got:

My next step would be to try to take some of their example code and get that working then look for differences in the requests, but that might take a lot of time.

epriestley edited this Maniphest Task.
epriestley edited this Maniphest Task.
epriestley edited this Maniphest Task.