Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of martinh@gmail.com designates
 209.85.161.52 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type;
        b=IVbwD+YmcXu5320Vj6MWyHXhYj3G/oVPiO04fbPr04AIHHJjQw9Xa+k80ITvaed7YW
         zdUmui4zVK3SFXXgsrjfLTUs2bZEpXrsH/2+k+XdBzsaJ/TLtRqEo9Gy3KwpqKJSV02R
         Y5+/BVTXOBQpZUKyW6ttURacjiG2sTX46qqX4=
MIME-Version: 1.0
Sender: martinh@gmail.com
In-Reply-To: <4C10E630.5090902@hotornot.de>
References: <4C10E630.5090902@hotornot.de>
Date: Thu, 10 Jun 2010 15:17:38 +0100
Message-ID: <AANLkTimLk-SkZ4KqxU3IOifFYHkYsViXnLr6nhwp3UIF@mail.gmail.com>
Subject: Re: Authentication
From: Martin Higham <martin@ocasta.co.uk>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=0016e6da7aef4ee5c30488adaf05

--0016e6da7aef4ee5c30488adaf05
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

The best I found was
http://wiki.apache.org/couchdb/Authentication_and_Authorization but that's
not much to go on.

I've therefore spend a little time trying to understand what and how it
works. The oauth.ini file contains all the keys, tokens and secrets. Within
that there are three sections

[oauth_consumer_secrets]
defines the oauth_consumer key/secret pairs (client credentials) for any
oauth clients you want to allow to connect

[oauth_token_users]
Maps oauth access tokens to CouchDB usernames

[oauth_token_secrets]
Maps oauth access tokens to their respective secret.

Luckily in 0.11 all of these can be changed and set via the _config api. Tr=
y
from Futon to find the exact calls

If the client has its client credentials and a user's access token and
secret then using standard oauth libraries any request can be oauth signed
and authenticated (as the example in the wiki demonstrates)

There are two _oauth special URLs _oauth/request_token and _oauth/authorize
but I remain to be convinced that these work. I have only got calls
to _oauth/request_token to return a valid response when signing the request
with the client and access keys/secrets and the test cases do the same.

There is nothing in place (or at least I haven't found it) to assist in key=
,
token or secret creation or to support the full three-legged authentication
where a user is required to authorise a client to authenticate on their
behalf.

Martin


On 10 June 2010 14:18, Markus Wolf <m.wolf@hotornot.de> wrote:

> Hi,
>
> is there some documentation on how to configure the oauth in couchdb?
> We would like to create some kind of single sign on for our app which
> uses couchdb.
>
> Regards
> Markus
> --
> Markus Wolf
> Entwicklung
>
> FaceValue Media GmbH
> Max-Brauer-Allee 34
> 22765 Hamburg
> Fon: +49 (0) 40 1888899-73
> Fax: +49 (0) 40 1888899-873
> E-Mail: m.wolf@hotornot.de
>
> http://www.HOTorNOT.de - Europe's #1 rating site
> Sitz der Gesellschaft: Breslauer Strasse 39
> 65830 Kriftel
>
> Amtsgericht Frankfurt/M HRB 54159, UST-ID: DE 223646709
> Gesch=E4ftsf=FChrung: Frank B=F6hmer
>

--0016e6da7aef4ee5c30488adaf05--