OAuth mechanism.

[Patrick Ben Koetter]

* William Mills <wmills at yahoo-inc.com>:
> How solid does this need to be prior to getting submitted back?  Is
> there a referred source code repo to use (Sourceforge, code.google.com,
> ...)? 

It should come with documentation. At the very minimum a test file (see:
saslauthd.txt) that describes the parameters, their options and their
meanings. At best you provide this and an instruction that tells how to put
the pieces together.

p at rick


> 
> The code still has some warts in it and wants some thought on things
> like where credentials get cached and such.  Also need an open OAuth API
> to build against for the server side (Client doesn't need that).
> 
> -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
> > 
> > 

-- 
All technical questions asked privately will be automatically answered on the
list and archived for public access unless privacy is explicitely required and
justified.

saslfinger (debugging SMTP AUTH):
<http://postfix.state-of-mind.de/patrick.koetter/saslfinger/>