[
https://issues.apache.org/jira/browse/COUCHDB-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759098#action_12759098
]
Benoit Chesneau commented on COUCHDB-512:
-----------------------------------------
@janl i'm agree, was just asking. Even if I think having auth per db in one db
sound more natural : since you replicate per db not having auth replicated with
it, is weird.
Per db we could have an _acl doc + _user/id docs containing users, _users and
_acl could be only changed by the owner of the db.
Speaking about replication maybe the right to replicate was forgotten ? Maybe
someone could read, write but not replicate and vice-versa ?
Thinking about db matching I wonder why not puting acls in different docs and
having a view matching dbs ? Since matching is already handled by couchdb. It
won't match * though or maybe there could be a special match for that ? At
least for auths per db in one generic db. Also thinking about that what if the
number of db is big ? having acl per db splitted in differents docs may help.
> Per-DB Authorization and ACL
> ----------------------------
>
> Key: COUCHDB-512
> URL: https://issues.apache.org/jira/browse/COUCHDB-512
> Project: CouchDB
> Issue Type: New Feature
> Components: Database Core
> Reporter: Jason Davies
> Fix For: 0.10
>
> Attachments: per_db_auth.patch
>
>
> Following discussions on the mailing list, this is for tracking work and
> comments surrounding an implementation of per-db authorization and ACL.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
