#768 closed defect (fixed) now supports oauth, but oauth token has twitter token url?

Reported by: Joshua R. Poulson <jrp@…> Owned by:
Priority: normal Milestone:
Component: BitlBee Version: 3.0.1
Keywords: oauth Cc:
IRC client+version: irssi Operating System: Linux
OS version/distro:


Enable oauth for working account: account # off account # set oauth true account # on go to url that is msg'd to you (on twitter?) get pin, response to msg with pin account # off Account # on oauth authentication fails and no oauth is reigstered on

Attachments (0)

Change History (9)

comment:1 Changed at 2011-03-17T13:50:17Z by anonymous

The reason for this is that in protocols/twitter/twitter.c the urls for oauth are hardcoded into the (static const) struct twitter_oauth

Instead, for, and other StatusNet-derived services which use the Twitter protocol, these URLs should be settable parameters.

comment:2 Changed at 2011-03-26T17:00:05Z by wilmer

Got a link for OAuth details? API URLs, getting API keys, etc?

comment:3 Changed at 2011-03-26T18:54:47Z by Joshua R. Poulson <jrp@…>

Well, the link for setting up an oauth app is here: gives a particular user's list of registered oauth apps.

The api root for is other StatusNet sites can be figured out using API discovery:

The StatusNet discussion of oauth API support is here:

comment:4 Changed at 2011-03-26T19:05:55Z by Joshua R. Poulson <jrp@…>

Looking at protocols/twitter/twitter.c I'd say this is getting close (not sure if the keys made sense, so I blanked them out, since it's likely the app would have to be registered).

static const struct oauth_service identi_ca_oauth = {

"", "", "", .consumer_key = "", .consumer_secret = "",


Of course, is not the only StatusNet service...

comment:5 Changed at 2011-03-26T20:32:54Z by Wilmer van der Gaast <wilmer@…>

I requested API keys/etc and added the right URLs + glue code but am getting "invalid signature" complaints. Can't really see what I'm doing differently and know this code does work with Twitter. I'm a bit out of guesses on what could be the problem here now.. :-(

comment:6 Changed at 2011-03-27T14:08:26Z by wilmer

I give up on this for now. bti (OAuth-enabled twitter/identica client) can log in, BitlBee can't. But if I use an access token from bti in BitlBee it logs me in and everything works.

ac 7 set password oauth_token=<token>&oauth_token_secret=<secret>

I guess I'll submit what I have now at least. Every operation works perfectly except converting the PIN into access credentials. The same code works for everything in Twitter. I don't know where the bug is or if it's even in BitlBee. I don't use myself so I hope someone else who cares more about this can take a look.

comment:8 Changed at 2011-12-21T19:47:23Z by wilmer

changeset:xmpp-oauth,828 should fix this. Looks like Twitter's OAuth implementation accepts two (or maybe even more?) signatures to deal with buggy clients and thanks to that I never discovered BitlBee's OAuth implementation was in fact buggy.

I can't test this against now, but this fix made accept my signature. If someone here could test this against once they're up again and report here, that'd be great.

comment:9 Changed at 2012-03-12T23:52:33Z by wilmer

Resolution: fixed
Status: newclosed

3.0.5 fixes this. Just make sure you use "Account add identica", not a twitter acct with changed base_url setting.

Modify Ticket

as closed The ticket will remain with no owner.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.