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

Elliot Murphy commented on COUCHDB-478:
---------------------------------------

When running tests in futon against this patch applied to an svn snapshot of 
svn rev 805910 on ubuntu karmic I get two test failures:

in the replication tests:
{"message":"docB is 
null","fileName":"http://127.0.0.1:5984/_utils/script/couch_test_runner.js","lineNumber":53,"stack":";([object
 Object],[object 
Object])@http://127.0.0.1:5984/_utils/script/couch_test_runner.js:53\u000a((void
 
0))@http://127.0.0.1:5984/_utils/script/couch_test_runner.js:66\u000arun(-1)@http://127.0.0.1:5984/_utils/script/couch_test_runner.js:78\u000a"}

and in the oauth tests:

# Assertion failed: xhr.status == expectedCode
# Assertion failed: xhr.status == expectedCode
# Assertion failed: xhr.status == expectedCode
# Assertion failed: xhr.status == expectedCode
# Assertion failed: xhr.status == expectedCode
# Assertion failed: xhr.status == expectedCode
# Assertion failed: xhr.status == expectedCode
# Assertion failed: xhr.status == expectedCode

> Modify couch_httpd_auth:get_user to read from [admins] in .ini config and 
> fall back to using database
> -----------------------------------------------------------------------------------------------------
>
>                 Key: COUCHDB-478
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-478
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: HTTP Interface
>            Reporter: Jason Davies
>             Fix For: 0.10
>
>         Attachments: oauth_ini_users.patch
>
>
> In the future we will make this pluggable (and orderable) but for now I think 
> it is a sensible default to make oauth and cookie auth respect [admins] in 
> the .ini as well as reading users from the database.

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

Reply via email to