[
https://issues.apache.org/jira/browse/COUCHDB-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14205664#comment-14205664
]
Mike Wallace commented on COUCHDB-2452:
---------------------------------------
The above commits get the tests in share/www/script/test/users_db_security.js
passing against the clustered port. I haven't figured out an elegant way of
getting the tests to run first against an authentication DB on the admin port
and then on the clustered port so currently I am testing it by applying a
rather ugly hack to the javascript tests [1].
These commits aren't quite ready for review - now that the tests are passing
I'd like to go over them with a fresh pair of eyes and make sure I'm happy with
the approach being taken for the fixes.
[1] https://gist.github.com/mikewallace1979/26ab223d3d0cfa372acb
> 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)
