From dev-return-48392-archive-asf-public=cust-asf.ponee.io@couchdb.apache.org Thu Feb 28 10:49:13 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id D2C51180657 for ; Thu, 28 Feb 2019 11:49:12 +0100 (CET) Received: (qmail 13016 invoked by uid 500); 28 Feb 2019 10:49:11 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 13000 invoked by uid 99); 28 Feb 2019 10:49:11 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Feb 2019 10:49:11 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 4B394C9799 for ; Thu, 28 Feb 2019 10:49:11 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.973 X-Spam-Level: X-Spam-Status: No, score=0.973 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id LCEI2GnKn968 for ; Thu, 28 Feb 2019 10:49:09 +0000 (UTC) Received: from monoceres.uberspace.de (monoceres.uberspace.de [95.143.172.184]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 968805F643 for ; Thu, 28 Feb 2019 10:41:28 +0000 (UTC) Received: (qmail 3136 invoked from network); 28 Feb 2019 10:41:27 -0000 Received: from localhost (HELO ?IPv6:2a02:8106:1d:4a00:843:8af7:ce8c:7ae5?) (127.0.0.1) by monoceres.uberspace.de with SMTP; 28 Feb 2019 10:41:27 -0000 From: Jan Lehnardt Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 12.1 \(3445.101.1\)) Subject: Re: [DISCUSS] Per-doc access control Date: Thu, 28 Feb 2019 11:42:41 +0100 References: <0115BBC5-B7C9-4887-9F93-1DE46146ADAD@apache.org> <40915025-DDBF-4291-8C7C-7CC69EB326A8@apache.org> <5C217847-5E47-43E5-AB13-DCE069DC813A@apache.org> <21E6C2A4-A22E-4A29-91FD-4FB113B8684C@apache.org> <4830984F-7864-40F7-8462-D239C16BF30F@apache.org> <0C75EA90-9796-4CA4-84A9-D2EE06835963@apache.org> To: CouchDB Developers In-Reply-To: <0C75EA90-9796-4CA4-84A9-D2EE06835963@apache.org> Message-Id: <0A3566F7-64AA-4972-B378-860B0E5D34F0@apache.org> X-Mailer: Apple Mail (2.3445.101.1) Hanks Adam and Robert for sorting this one. Michael, the idea is to give mutually untrusting users access a = as-close-to-verbatim-CouchDB API to their section of a shared database. = So you get full doc CRUD, _changes, views, replication, the lot, but = only for documents that you have access to. So there is no sneaking = behind the back and getting all the data, if you don=E2=80=99t already = have access to it, in which case you already have access to them :) Best Jan =E2=80=94 > On 27. Feb 2019, at 22:55, Adam Kocoloski wrote: >=20 >=20 >> On Feb 27, 2019, at 3:47 PM, Michael Fair = wrote: >>=20 >>>=20 >>>=20 >>>> This might be what is already planned (it hasn't sounded like it to = me >>>> though). >>>> And I definitely think changing the perspective to make "databases" = a >>>> function of the access control system and to make views based on = "access >>>> controlled collection results" instead of "databases" would be = quite >>>> powerful... >>>>=20 >>>> Regards, >>>> Mike >>>=20 >>> Hi Mike, what you=E2=80=99ve described here is very very similar to = what Jan is >>> building. >>>=20 >>> Adam >>>=20 >>>=20 >> I read back through the links that Jan posted again; the details I = was >> looking for are probably somewhere in the sharding conversation that = my >> eyes glazed over on or somewhere in the notes of the roadmap = discussion >> which made it a bit hard for me to find just the parts related to = this (I >> most likely scrolled through it). ;-) >>=20 >> Thanks for clarifying for me, and for letting me chime in! >>=20 >> Mike >=20 > Those details are really hard to find =E2=80=94 I can only find them = because I know exactly where to look in the minutes of a meeting that I = attended well over a year ago :) Probably a good case for an RFC so we = have a current pointer to the plan. >=20 > Adam --=20 Professional Support for Apache CouchDB: https://neighbourhood.ie/couchdb-support/