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 jchris@gmail.com designates
 209.85.221.21 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
         :content-transfer-encoding;
        b=BoT72iEEog15N0KA12q/Y5dTf9OXEDZDn4O2srTT1UNtpDfYPHHaBzFUSNljVV+ISH
         96ObHctq/nc0S8GGrMoW57Xh5NHe+6JawelTO9gqovn7J5/Vg0A/LKrVwMqpc7jmOgSX
         ydGch12bfoXvlURsSr+ix1rIismjupF00ZKc8=
MIME-Version: 1.0
Sender: jchris@gmail.com
In-Reply-To: <8B682F8E-52E1-4A41-BDA9-5168FFAC3E0A@mooseyard.com>
References: <7C8D756C-FD0A-4665-8583-49F992973138@mooseyard.com>
	 <5118A1E1-A51C-4722-BBA8-71F6FAF6B181@apache.org>
	 <09BA5434-3B20-42D0-8450-06E25993BF9C@mooseyard.com>
	 <9E984EC0-80EE-4A1F-8E9A-35E5E9C139B9@apache.org>
	 <201E60EA-30E9-4B3A-A994-3688A8544BCA@apache.org>
	 <8B682F8E-52E1-4A41-BDA9-5168FFAC3E0A@mooseyard.com>
Date: Sun, 15 Feb 2009 14:57:09 -0800
Message-ID: <e282921e0902151457v83b88edg37889376a4e1bb9d@mail.gmail.com>
Subject: Re: Getting "unauthorized" errors replicating from jchris's
	twitter-client-design
From: Chris Anderson <jchris@apache.org>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On Sun, Feb 15, 2009 at 2:46 PM, Jens Alfke <jens@mooseyard.com> wrote:
>
> On Feb 15, 2009, at 2:30 PM, Damien Katz wrote:
>
>> Jan is correct. This looks to be because design doc is replicating, which
>> requires a security check. If the target replica has on admin security
>> turned, this will break. The security patch is meant to deal with these
>> issues.
>
> By "target" do you mean the source or destination of the replication? The
> destination db (mine) has access protection enabled too, but from Jan's
> previous answer it sounded like the issue was with the source db (jchris's
> public server) being write-access controlled.
>

The issue is that the validation function does not allow docs to be
saved by other users than than the user listed as the doc author. This
makes total sense for editing docs, but breaks down in that it does
not allow docs created by the author on my machine, to be saved by
replication into the db on your machine, unless you are logged into
your machine as me.

(OK I just realized that I'm probably talkng about Sofa's db
http://jchrisa.net/drl and not the Twitter client.

The twitter-client design doc
http://jchrisa.net/twitter-client/_design/twitter-client has no
validation function. It could be a different issue. Also my couch is
running on not-quite-trunk ATM...

Chris

-- 
Chris Anderson
http://jchris.mfdz.com