Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4CD4064B.5020903@free.fr>
Date: Fri, 05 Nov 2010 14:27:39 +0100
From: cdr53x <cdr53x@free.fr>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
 rv:1.9.1.15) Gecko/20101027 Thunderbird/3.0.10
MIME-Version: 1.0
To: user@couchdb.apache.org
Subject: Document security, restricting document viewers
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hello,

I'd like to know what is your advice on implementing a security system 
that would provide two simple roles for couch db documents :

  - document writer
  - document reader

The idea is of course to limit the access of a given doc and allow it 
only on certain users.

I know that the 'writer' role can be implemented using validation hooks, 
as explained in the docs, however there is not a clue on what 
could/should be done in order to protect the documents from being viewed.

Is there anything existing that could be used and that I missed in the 
docs ?

If not are there any advices on implementing such a feature ?

Of course, the idea is to be able to address large databases, ( ~ 1.2M 
docs ), with large views,  so there is no way an client side ( or server 
side ) application could cross check the right of each element returned 
by a view.

If anyone has any suggestion on this, I'd realy appreciate

Regards,

cdrx