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.214.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=otb1il3D61N4Mj9pSpAsmlg6+niSfgw3Z70jE9CcO+JGkc6EDfp1iOCPajqjXzTEsO
         iolUqp5EtV1ecEi8JHFSlhA7cYBV9Otz0XwLbtXdJ7eUph1D9NJhlPO3kLuOmYz24m5g
         ydCPOvIPedJbSitvcL2VmGemyZnn4n92IEoS8=
MIME-Version: 1.0
Date: Fri, 6 Aug 2010 13:25:10 +0200
Message-ID: <AANLkTimEptvJCvPagJbEHDHyirh-7Tv+AFxtQaTrF9rR@mail.gmail.com>
Subject: path based authentification in rewriter
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 written this patch sometimes ago that add path authentification
to _rewrite handler :


http://github.com/benoitc/couchdb/commit/9c15cf8ed710db3805bd1a7d792ba53457=
cb9c48


So if you have a rule :

{
  "from": "/somepath",
  "to": "/path",
  "roles": ["_admin", "somerole"]
}

It will test user roles against this patch and allow the use to see the
result only if he's authorized. It handle only roles for now, but adding
usernames could be easy too.

Do you think It worth to make it upstream ? (ie commit it in trunk)

Let me know.

- beno=EEt