[
https://issues.apache.org/jira/browse/COUCHDB-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14234161#comment-14234161
]
ASF GitHub Bot commented on COUCHDB-2452:
-----------------------------------------
GitHub user mikewallace1979 opened a pull request:
https://github.com/apache/couchdb-couch-mrview/pull/11
Export get_view_callback/3 for use by chttpd
In order to provide the expected security for the _users DB on
the clustered interface, chttpd needs to use get_view_callback/3
so it can use either view_cb/2 (normal case) or filtered_view_cb/2
(for the _users DB).
COUCHDB-2452
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/couchdb-couch-mrview
2452-users-db-security-on-clustered-interface
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/couchdb-couch-mrview/pull/11.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #11
----
commit 53302fbe52b2a8375297edc003f5fc7cd261b9ed
Author: Mike Wallace <[email protected]>
Date: 2014-11-10T23:44:47Z
Export get_view_callback/3 for use by chttpd
In order to provide the expected security for the _users DB on
the clustered interface, chttpd needs to use get_view_callback/3
so it can use either view_cb/2 (normal case) or filtered_view_cb/2
(for the _users DB).
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)
