Thanks so much.. the first link opened my eyes. ;-)
2010/10/29 Zachary Zolton <[email protected]> > Matthias, > > So it sounds like you need to setup individual user accounts and give > each of them their own database. Then add the user ID to the "readers" > array in the security object for their database. That will stop anyone > else from being able to read/write to the user's database. > > You can read more about the security object here: > http://wiki.apache.org/couchdb/Security_Features_Overview#Authorization > > Also, here's a pretty good overview of CouchDB security: > > http://blog.couchone.com/post/1027100082/whats-new-in-couchdb-1-0-part-4-securityn-stuff > > > Cheers, > > Zach > > > On Fri, Oct 29, 2010 at 5:49 AM, Matthias Nothhaft > <[email protected]> wrote: > > Hi, > > > > I would like to know if it's possible to setup CouchDB so that I can have > > different users for different databases. So that user A can only access > > database A (read, write, create design docs, etc). > > > > Somehow I didn't find a proper solution yet. It also does not make sense > to > > me to put this kind of security checks into design docs. > > > > Is there a clean and secure way to setup an environment for CouchDB > hosting? > > Maybe by running different instances for different databases? Or is this > > just not possible? > > > > regards, > > Matthias Nothhaft > > >
