identi.ca now supports oauth, but oauth token has twitter token url?

[Joshua R. Poulson <jrp@…>]

Enable oauth for working identi.ca 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 identi.ca

[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 indenti.ca, and other StatusNet-derived services which use the Twitter protocol, these URLs should be settable parameters.

[wilmer]

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

[Joshua R. Poulson <jrp@…>]

Well, the link for setting up an oauth app is here: ​http://identi.ca/settings/oauthapps/new

​http://identi.ca/settings/oauthapps gives a particular user's list of registered oauth apps.

The api root for identi.ca is ​http://identi.ca/api other StatusNet sites can be figured out using API discovery: ​http://status.net/wiki/API_discovery

The StatusNet discussion of oauth API support is here: ​http://status.net/wiki/Twitter-compatible_API#OAuth_resources

[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 = {

"​http://identi.ca/api/oauth/request_token", "​http://identi.ca/api/oauth/access_token", "​https://identi.ca/api/oauth/authorize", .consumer_key = "", .consumer_secret = "",

};

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

[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.. :-(

[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 identi.ca myself so I hope someone else who cares more about this can take a look.

[wilmer]

changeset:devel,774

[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 identi.ca now, but this fix made ​http://term.ie/oauth/example/ accept my signature. If someone here could test this against identi.ca once they're up again and report here, that'd be great.

[wilmer]

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