You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@couchdb.apache.org by Apache Wiki <wi...@apache.org> on 2010/12/21 12:58:49 UTC

[Couchdb Wiki] Update of "PerDocumentAuthorization" by BramNeijt

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Couchdb Wiki" for change notification.

The "PerDocumentAuthorization" page has been changed by BramNeijt.
http://wiki.apache.org/couchdb/PerDocumentAuthorization?action=diff&rev1=5&rev2=6

--------------------------------------------------

  
  = Possible solutions =
  == Database per user ==
- Create one database for each user and use authentication on the database for that given user. Because views do not work across databases, you will have to replicate all needed data between the different user databases to allow for a view to contain both private and public/other users' data.
+ Create one database for each user and use authentication on the database for that given user. Because views do not work across databases, you will have to replicate all needed data between the different user databases to allow for a view to contain both private and public/other users' data. Because normal users can not create/delete databases, you will need to have a separate process running which watches your database for changes and creates a new user database when a new user registers.
  
  Access protection this solution implements:
   * Update: completely, the database can be protected against other users writing into it.