Skip Menu |

This queue is for tickets about the LWP-Authen-OAuth CPAN distribution.

Report information
The Basics
Id: 71348
Status: resolved
Priority: 0/
Queue: LWP-Authen-OAuth

People
Owner: Nobody in particular
Requestors: BitCard [...] ResonatorSoft.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Support for OAuth 2.0
This module looks great, since it slides right into LWP. However, Google, Facebook, and various others have already implemented OAuth 2.0, as the draft is almost finished. I've heard that the implementation is actually easier, since OAuth 1.0 was so complicated, so maybe it's easier to implement. Is this something that you've researched?
On Thu Sep 29 19:54:12 2011, SineSwiper wrote: Show quoted text
> This module looks great, since it slides right into LWP. However, > Google, Facebook, and various others have already implemented OAuth
2.0, Show quoted text
> as the draft is almost finished. I've heard that the implementation
is Show quoted text
> actually easier, since OAuth 1.0 was so complicated, so maybe it's > easier to implement. > > Is this something that you've researched?
This module hides the difficulties of OAuth 1. The downside to this module is it isn't actually an LWP::Authen module, but a wrapper for LWP::UserAgent - my fault for not RTFM. OAuth 2 is a completely new protocol. From my understanding, it's the difference between signing a message (OAuth 1) and passing temporary authentication credentials (OAuth 2). This module will never support OAuth 2. If I ever have a need to use OAuth 2 e.g. if Google drop support for OAuth 1, I'll look into building a separate OAuth 2 authenticator.