Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <4E25493B.9040907@yooook.net>
Date: Tue, 19 Jul 2011 11:07:07 +0200
From: Camille Harang <mammique@yooook.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.9.2.17) Gecko/20110516 Icedove/3.1.10
MIME-Version: 1.0
To: dev@couchdb.apache.org
Subject: Re: OAuth for authorization (not authentication)
References: <4E2433C8.3040200@yooook.net>
 <CABvT1DETV7VxK9_biM1WzC0BH6Y1-e=TNb4LQriiMSTFuWQyRw@mail.gmail.com>
In-Reply-To: 
 <CABvT1DETV7VxK9_biM1WzC0BH6Y1-e=TNb4LQriiMSTFuWQyRw@mail.gmail.com>
OpenPGP: id=4AF32373;
	url=
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

Hi again,

Le 18/07/2011 15:44, Robert Newson a �crit :
> As also noted on IRC, you are indeed wrong,

I hope I am, I really tried to find the proper way to fully implement
OAuth authorization layer (tokens, ad hoc grant access in time and
scope: the very essence of OAuth) within the CouchDB intrinsic
techniques and philosophy, but I keep failing.

> you just don't like the
> granularity

I don't dislike or like it, but wherever I look it just appears to me
that there is just not enough of it to match the requirements of a
proper implementation of OAuth. But I believe being wrong, I'm sure I
am, I want to use Couch, can anyone point me the right direction? Once I
know it, I will like it.

Thanks,

Cheers,

Camille.


>  of the operation you are authorized to perform after
> successfully authenticating. :)
>
> B.

-- 
The Good, the Bad and the Ugly under Creative Commons! https://yooook.net/r/lp1