Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3775890AC for ; Tue, 29 May 2012 11:43:03 +0000 (UTC) Received: (qmail 95481 invoked by uid 500); 29 May 2012 11:43:01 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 95443 invoked by uid 500); 29 May 2012 11:43:01 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 95431 invoked by uid 99); 29 May 2012 11:43:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 May 2012 11:43:01 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of kxepal@gmail.com designates 209.85.215.180 as permitted sender) Received: from [209.85.215.180] (HELO mail-ey0-f180.google.com) (209.85.215.180) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 May 2012 11:42:55 +0000 Received: by eaai12 with SMTP id i12so1095953eaa.11 for ; Tue, 29 May 2012 04:42:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=7TZUL/mdE2oCt/7FBNRogGnh0rXk3/4yAfaZ4Yojqs8=; b=YH/s3qsqnnCx0m4235utljPXRI7EEFxgK+Ri3Z+QEGIXkIkQheIgLTJZ55bBg7mMg+ /VebgoVMKAf8cqdyD7NppWSbNlsln4FIuZWMHtZoPRG18kZambaXyEPq+bUOqidrhED4 gVcIF6FmBWZnHTv48uwy6iAWRCypB1r4gB/VLuIODaZsIK7Yge95Pnw2uZ9czgy22HrZ 4Eq68iDbpGEuAZKAyCgNEMlJtAIiLrfyqBJOv+0h6MG7vQKRAxEUghkLQXn44cTIerlT 5oxRggSbAMv0NA/ZPDrkwFy64EjtARy0Ruf8Ixq6JLDW8inyHIUtNdnb+9iz1XCPy9RK didg== MIME-Version: 1.0 Received: by 10.14.99.11 with SMTP id w11mr3914215eef.67.1338291753849; Tue, 29 May 2012 04:42:33 -0700 (PDT) Received: by 10.14.43.19 with HTTP; Tue, 29 May 2012 04:42:33 -0700 (PDT) In-Reply-To: <4FC4B330.3000503@gmail.com> References: <4FC4B330.3000503@gmail.com> Date: Tue, 29 May 2012 15:42:33 +0400 Message-ID: Subject: Re: security: disable GET to some user From: Alexander Shorin To: user@couchdb.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Hi, While you'd like to disable GET for some users for some doc with _id: "foo" he could alternatively get it via: curl -X POST http://localhost:5984/db/_all_docs?include_docs=3Dtrue -d '{"keys":["foo"]}' -H "Content-Type: application/json" Same works for other views. Probably, "per-user db" or "per-usergroup db" design would be much more better solution. -- ,,,^..^,,, On Tue, May 29, 2012 at 3:29 PM, Alessandro wrote: > Hi all, > =C2=A0 I'm "exploring" couchdb, and I'd like to know how can I use as fro= nt-end > also. > > So I think I need to disable the reading of some document to some > users/roles/groups. > > Is this possible? Or have I to use a different front-end? > > Thanks > Alessandro