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 dave@muse.net.nz designates
 209.85.220.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CADA=EV9TtV8QNrfzBbPKgHs6eB1AbwWojHjYzaFz6qUgBW4xHQ@mail.gmail.com>
References: 
 <CADA=EV9TtV8QNrfzBbPKgHs6eB1AbwWojHjYzaFz6qUgBW4xHQ@mail.gmail.com>
Date: Wed, 20 Jun 2012 22:34:23 +0200
Message-ID: 
 <CAHZBNKYu9cPi5a9gitB3Y11u7328GNVizc0RUNx-j_96c0HfkQ@mail.gmail.com>
Subject: Re: Replication and validate_doc_field
From: Dave Cottlehuber <dave@muse.net.nz>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On 20 June 2012 22:22, Pulkit Singhal <pulkitsinghal@gmail.com> wrote:
> Does validate_doc_field method affect replication authN or authZ for
> CouchDB 1.2.0?

Hey Pulkit,

I googled authN/Z and found authorisation and authentication. I checked
the source and there's no validate_doc_field.

A validate_doc_update function (VDU) is run on a single doc only, and
has access to the proposed new doc as well as the current on-disk version,
and the user context.

So you can tell if the submitter of the update is authenticated or not, and
you can use couchdb roles, or other custom javascript fields in your doc
to decide to reject the docs or not.

There's more info on both the wiki and the definitive guide on this too.

A+
Dave