[
https://issues.apache.org/jira/browse/COUCHDB-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14234119#comment-14234119
]
ASF subversion and git services commented on COUCHDB-2452:
----------------------------------------------------------
Commit ed4a4a9e2bfbc906bc2339007fe7ef13137eba88 in couchdb's branch
refs/heads/2452-users-db-security-on-clustered-interface from [~mikewallace]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb.git;h=ed4a4a9 ]
Make users_db_security.js use N=1 clusters only
The users_db_security.js test will not work against a multi-node
cluster because it relies on config settings being made by the
test code. Because there is no generic way of discovering the
locations of the other nodes on a dev cluster (they may be on
unexpected ports for one reason or another) it is only possible
to guarantee those settings are made on a single node.
This commit therefore forces the users_db_security.js test to run
against a single node cluster by:
- setting the cluster variables to N=Q=R=W=1
- excluding the test in the Makefile and running it explicitly
with `dev/run -n 1`
- teaching run_on_modified_server to correctly preserve the old
config settings when nested run_on_modified_server calls are
made
COUCHDB-2452
> Provide _users DB security when _users DB is on the clustered interface
> -----------------------------------------------------------------------
>
> Key: COUCHDB-2452
> URL: https://issues.apache.org/jira/browse/COUCHDB-2452
> Project: CouchDB
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: Database Core
> Reporter: Mike Wallace
>
> The authentication DB (default name _users) has special security semantics
> which are currently only supported on the admin port (default 5986). Since we
> support using the _users DB on the clustered port we should also ensure the
> same security semantics apply there.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
