[
https://issues.apache.org/jira/browse/COUCHDB-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287531#comment-15287531
]
Sebastian Rothbucher commented on COUCHDB-2991:
-----------------------------------------------
I guess there is no much more 2 do from the test side anyway ;-) (the
users_db_security test just uncovered sth - and skipping that yields one more
issue with DB admin no more possible for _users (see
https://github.com/sebastianrothbucher/couchdb/commit/aef6837b1660032a47bb52ebcc7eabbdfafec35c).
If that is fixed and stabilized, one seems to be through
> userdb behaves less strict on cluster
> -------------------------------------
>
> Key: COUCHDB-2991
> URL: https://issues.apache.org/jira/browse/COUCHDB-2991
> Project: CouchDB
> Issue Type: Bug
> Reporter: Sebastian Rothbucher
> Priority: Minor
>
> Topic #1: _design/auth does not get installed on custom users DB
> To reproduce: set both
> [{section: "couch_httpd_auth",
> key: "authentication_db", value: usersDb.name},
> {section: "chttpd_auth",
> key: "authentication_db", value: usersDb.name}]
> to a usersDB that is not _users and check if the document is there (certainly
> minor)
> Topic #2: conflicts in user docs don't seem to bother any longer
> To reproduce: produce a conflict in a user doc (the users_db.js test does
> that also) and try to login (which works)
> Topic #3: any user can call _all_docs on _users via cluster port (not
> backdoor)
> To reproduce: create a user doc and use it to get _users/_all_docs (once on
> cluster, once on backdoor), you'll see the difference: cluster allows the
> action while backdoor does not
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
