Feature request: OAuth authentication

[GoogleCodeExporter]

Laconica and Twitter support OAuth for accessing an account. It would be
preferable to use this in Pidgin instead of username/password.

Original issue reported on code.google.com by chaz6....@gmail.com on 20 Aug 2009 at 8:27

[GoogleCodeExporter]

This is in our consideration sometime. With OAuth, seems that user will instead 
have
to copy authentication token to Pidgin instead of just input username/password. 
IMO
this might not suitable for desktop application.

My idea is that we will support OAuth as alternative, but the same 
username/password
will remains. At least until all services drop support for username/password.

Original comment by somsaks on 20 Aug 2009 at 9:01

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

I am not sure about Laconica but Twitter supports the OAuth PIN mechanism for 
desktop
applications so you do not need to mess about with tokens.

Original comment by chaz6....@gmail.com on 20 Aug 2009 at 10:48

[GoogleCodeExporter]

twitter is ending basic auth in June, and _forcing_ every 3rd app to use OAuth.
Now is the time to update mbpurple.

Original comment by BUGabu...@gmail.com on 23 Apr 2010 at 12:21

[GoogleCodeExporter]

Done in SVN. Oauth token request and authentication work. 

Original comment by somsaks on 25 May 2010 at 6:55

• Changed state: Fixed

[GoogleCodeExporter]

YAY
when can we expect this in the PPA?
I'm volunteering to test it

Original comment by BUGabu...@gmail.com on 25 May 2010 at 11:04

[GoogleCodeExporter]

Issue 96 has been merged into this issue.

Original comment by andresen.nils@gmail.com on 7 Feb 2011 at 9:09