[jira] [Commented] (COUCHDB-2452) Provide _users DB security when _users DB is on the clustered interface

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/COUCHDB-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14205649#comment-14205649 ] 

ASF subversion and git services commented on COUCHDB-2452:
----------------------------------------------------------

Commit 8c0299645e5ec0ea72de71c795c83a9b06d7b590 in couchdb-couch's branch refs/heads/2452-users-db-security-on-clustered-interface from [~mikewallace]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb-couch.git;h=8c02996 ]

Update auth DB docs via the auth module

Documents in the authentication DB were being updated directly
from couch_httpd_auth via couch_db:update_doc/3. This meant that
updates to documents with the authentication DB on the clustered
interface (5984) would fail.

This commit makes the auth module responsible for the document
update via a ?MODULE:update_doc/2 function and adds a function
for couch_httpd_auth which proxies to couch_db:update_doc/3.

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)