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

Robert Newson reassigned COUCHDB-1464:
--------------------------------------

    Assignee: Paul Joseph Davis

assigning to davisp as he has a replacement for the auth cache module.
                
> Unable to login to CouchDB
> --------------------------
>
>                 Key: COUCHDB-1464
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1464
>             Project: CouchDB
>          Issue Type: Bug
>    Affects Versions: 1.0.3
>         Environment: Apache CouchDB 1.0.1
> Ubuntu 10.04.2 LTS.
>            Reporter: Petter Olofsson
>            Assignee: Paul Joseph Davis
>
> Hi,
> Login to server with ordinary user accounts stopped working. Logging in with 
> admin's defined in local.ini still worked, but user account created as 
> documents always responded with username/password incorrect.
> When the old users did not work, we started to create new users in Futon. 
> Here are the requests from the logs when a user is created, and the failed 
> login afterwards.
> [Thu, 12 Apr 2012 14:22:57 GMT] [info] [<0.1392.0>] <ip> - - 'PUT' 
> /_users/org.couchdb.user%3Apetter 201
> [Thu, 12 Apr 2012 14:22:57 GMT] [info] [<0.1393.0>] <ip> - - 'POST' /_session 
> 401
> We restarted couch several times using
> $ service couchdb restart
> but it was still impossible to login with an ordinary user.
> The problem was resolved by changing the log level to "debug" in local.ini 
> and a restart.
> After this change the login and sign-up/in process in futon worked fine, and 
> the already created user account worked fine. 
> After changing the log level back to info the server continued to work fine.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to