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: <4E254F89.70207@yooook.net>
Date: Tue, 19 Jul 2011 11:34:01 +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>
 <4E25493B.9040907@yooook.net>
 <4AED7DD6-0911-484B-8A8B-10C1A6FF62D7@apache.org>
In-Reply-To: <4AED7DD6-0911-484B-8A8B-10C1A6FF62D7@apache.org>
OpenPGP: id=4AF32373;
	url=
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

Hi Jan, thanks a lot for your answer, even if that's what I dread :-/ I
hope I can find another way to make Couch match my needs (smart proxy
maybe). Otherwise I'll keep Couch in mind for my next project, hoping it
won't have the same requirements or if other solutions appears until
then, because Couch is such a good piece of software! I want to use it.
Thanks!

Cheers,

Camille.


Le 19/07/2011 11:20, Jan Lehnardt a �crit :
> Hi Camille,
>
> The OAuth implementation in CouchDB is very limited (due
> to constraints in the original development phase). The
> implementation does not allow fine-grained token-based
> access to specific contents of one or more databases
> inside CouchDB, but only the authentication against a
> CouchDB user in the CouchDB authentication layer. Once
> a request is auth'd, there is no more OAuth machinery
> inside CouchDB and you are left with CouchDB's security
> mechanics:
>
>   http://wiki.apache.org/couchdb/Security_Features_Overview
>   http://blog.couchbase.com/whats-new-in-couchdb-1-0-part-4-securityn-stuff
>
> Cheers
> Jan


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