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: domain of bchesneau@gmail.com
 designates 209.85.216.180 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        b=G/28o0xqTFnAid6KJu7SjrXelzi/UuwMhXfoMEe//gIcRxijxOVl2EXXiKTczoSova
         rUmxniQf1FLd7b87RmCywxGc5y9PyfU85RQPfutwEC/BHNZrhQ3Womvgg+ppr8dY0265
         zDDNLwRIaj5NyUFm4ijWlmtOMe0Aza6BG2Crs=
MIME-Version: 1.0
Date: Tue, 2 Feb 2010 15:57:50 +0100
Message-ID: <b7cd8ed11002020657o52a39d94wc8be7a2c2f3e038@mail.gmail.com>
Subject: [patch] proxy authentificationn handler
From: Benoit Chesneau <bchesneau@gmail.com>
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi all,

I've just pushed on jira my proxy authentification handler. This code
is used behind aimpl.org and works well.

https://issues.apache.org/jira/browse/COUCHDB-636

This handler allows creation of a userCtx objec from a user
authenticated remotly. The client just pass specific headers to
CouchDB and the handler create the userCtx. Headers name can be
defined in local.ini. By thefault they are :

* X-Auth-CouchDB-UserName : username, (x_auth_username in
couch_httpd_auth section)
* X-Auth-CouchDB-Roles : user roles, list of roles separated by a
comma (x_auth_roles in couch_httpd_auth section)
* X-Auth-CouchDB-Token : token to authenticate the authorization
(x_auth_token in couch_httpd_auth section). This token is an hmac-sha1
created from secret key and username. The secret key should be the
same in the client and couchdb node. secret key is the secret key in
couch_httpd_auth section of ini. This token is optional if secret key
isn't defined.

What do you think about including it in 0.11 ?

- beno=EEt