Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Message-ID: <314149176.552451269877948441.JavaMail.jira@brutus.apache.org>
Date: Mon, 29 Mar 2010 15:52:28 +0000 (UTC)
From: "Noah Slater (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Subject: [jira] Updated: (COUCHDB-438) Add per database (OAuth)
 authentication to couchdb
In-Reply-To: <1490312347.1248775035199.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/COUCHDB-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Noah Slater updated COUCHDB-438:
--------------------------------

    Fix Version/s:     (was: 0.11)
                   0.12

> Add per database (OAuth) authentication to couchdb
> --------------------------------------------------
>
>                 Key: COUCHDB-438
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-438
>             Project: CouchDB
>          Issue Type: New Feature
>    Affects Versions: 0.10
>            Reporter: eric casteleijn
>            Assignee: Jason Davies
>            Priority: Blocker
>             Fix For: 0.12
>
>
> In set-ups where a couchdb node holds databases for many different users that are not allowed to see each other's data, it is vital that it is possible to give users separate roles for each database. 
> It would be best if adding new users, and assigning roles to users for specific databases could be done through the http interface, as modifying .ini files becomes unwieldy for large numbers of users.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.