Hi Bram, cool to see your interest in contributing to the CouchDB project!
AFAIK we currently don't have read authorization on a per-document level. For write authorization on a per-document level we've got validation functions. See e.g. here: http://guide.couchdb.org/draft/validation.html and also here: http://wiki.apache.org/couchdb/Document_Update_Validation Recently, there has been reported an issue with it when replicating: https://issues.apache.org/jira/browse/COUCHDB-915 I haven't looked closely at it yet. However, it's really a major issue if validation functions don't work properly with replication, and it should get fixed then. Maybe you wanna take this as a starting point. Always feel free to ask questions or discuss with others in the #couchdb chatroom at freenode. Cheers, Klaus On Tue, 2010-10-26 at 11:51 +0200, Bram Neijt wrote: > Hi everybody, > > > I'm a developer at Xebia and I've been granted about 5 hours a week to > spend on implementing any open source project problem I would like to > see fixed. > > I've chosen to have a go at per document authorization for couchdb. > > As I'm weeding through the archives, I would love to hear about the > current approaches, who is involved, what is planned and what may be > considered an acceptable solution. > > > Looking forward to making a contribution, > > Bram
