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.212.52 as permitted sender)
MIME-Version: 1.0
Sender: martinh@gmail.com
In-Reply-To: 
 <CALnFx5pV9BOudpxgSjZxiUCFJZxMbA2puFPwQmGVaYnGazmpbg@mail.gmail.com>
References: 
 <CAD4-b-BqZREu_hGR0BCrd8_YxKReQcB_gvBbd4Hc9b6ZVXqUiw@mail.gmail.com>
	<CAD4-b-CB3mJx+syS7OU2XWmRU=OdG1gsT-yHa3Ke2UB-PcuK2w@mail.gmail.com>
	<CAAL6JQjMLkfQTQETPWE2btxSMZDpucUwowgC-p1X1MaLApCXjg@mail.gmail.com>
	<CALnFx5pV9BOudpxgSjZxiUCFJZxMbA2puFPwQmGVaYnGazmpbg@mail.gmail.com>
Date: Mon, 1 Aug 2011 18:40:42 +0100
Message-ID: 
 <CADR1q3DdF--Qo1H+kryAA8JkopyEgtnEhjqSbdN1buWxyZVu_g@mail.gmail.com>
Subject: Re: Implementing Authorization control for Self-Enrollers in a pure
 Couchapp
From: Martin Higham <martin@ocastalabs.com>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=20cf307f307e5f246604a9752143

--20cf307f307e5f246604a9752143
Content-Type: text/plain; charset=ISO-8859-1

Take a look at my example service in github

http://github.com/ocasta/CouchDB-Selfservice


On 1 August 2011 18:19, Jan Wedekind <jan.wedekind@gmail.com> wrote:

> On Tue, Jul 19, 2011 at 02:12, Randall Leeds <randall.leeds@gmail.com
> >wrote:
>
> > > ---------- Forwarded message ----------
> > > From: Alex Aitken <aaitken@alexaitken.net>
> > > Date: Thu, Jul 14, 2011 at 4:19 PM
> > > Subject: Implementing Authorization control for Self-Enrollers in a
> > > pure Couchapp
> > > To: dev@couchdb.apache.org
> > >
> > >
> > > What's the best way using CouchDB's built-in
> > > authentication/authorization to set up self-enrollers as user type =
> > > reader? I understand there's a db/_security object, but not how to
> > > edit it/use it/update it... And if admins are the only ones capable
> > > editing roles, how does a self-enrolled user get these assigned?
> > > Thanks for thoughts,
> > > Alex Aitken
> >
> > You can edit the _security object by clicking on "Security..." at the
> > top of the futon page for a database. You should also be able to
> > GET/PUT /database/_security.
> >
> > The rules for updating roles and who can change what about user
> > documents are actually just implemented as a validate_doc_update
> > function in the _users database.
> > Check out /_users/_design/auth. You could special case "readers" for
> > self-enrollment in your deployment.
> >
>
> I am kind of stuck at the same problem. I've looked at
> /_users/_design/_auth, which was quite insightful, thanks a LOT for that
> simple comment here.
>
> Alex, do I get correctly that you meant changing the validation functions
> so
> that users could set e.g. one specific role "reading" without throwing the
> error that only the admin may do that? Do you have an example for that?
>
> Many thanks,
> Jan
>

--20cf307f307e5f246604a9752143--