OAuth mechanism.

[William Mills]

Alexey,

Currently planning on Oauth 2.  I'll also implement Oauth 1.0a in all
likelihood.  The authenication is handled in an auxprop plugin and right
now I only have a stub for that, it accepts a base64 encoded JSON token
and anything that parses is accepted.

It still has a lot of rough edges.

-bill

> -----Original Message-----
> From: Alexey Melnikov [mailto:alexey.melnikov at isode.com] 
> Sent: Friday, July 16, 2010 4:08 PM
> To: William Mills
> Cc: cyrus-sasl at lists.andrew.cmu.edu
> Subject: Re: OAuth mechanism.
> 
> William Mills wrote:
> 
> > Hi,
> 
> Hi William, 
> 
> > I'm writing a SASL mechanism for OAuth as a reference 
> impelementation.  
> > Is that somethign that would get submitted back into the 
> core of Cyrus 
> > SASL or shoudl it live as a separate entity.  If it's a separate 
> > entity, are there other such opensource examples I can use 
> as a bassis 
> > for my packaging so I'm being consistent?
> 
> This sounds interesting enough, so I think it can be 
> committed to Cyrus SASL itself. Which specification are you 
> planning to implement?
> 
> Best Regards,
> Alexey
> 
>