Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Date: Wed, 7 Dec 2011 04:07:39 +0000 (UTC)
From: "Randall Leeds (Commented) (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: 
 <245289906.48259.1323230859940.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1370482061.47244.1323210160003.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (COUCHDB-1357) Authentication failure after
 updating password in user document
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Randall Leeds commented on COUCHDB-1357:
----------------------------------------

Patch looks good.
                
> Authentication failure after updating password in user document
> ---------------------------------------------------------------
>
>                 Key: COUCHDB-1357
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1357
>             Project: CouchDB
>          Issue Type: Bug
>    Affects Versions: 1.1.1
>            Reporter: Filipe Manana
>         Attachments: COUCHDB-1357-master.patch
>
>
> From the report at the users mailing list:
> http://s.apache.org/9OG
> Seems like after updating the password in a user doc, the user is not able to login with the new password unless Couch is restarted. Sounds like a caching issue.
> The only case of getting the cache consistent with the _users database content is if the _users database processes crash and after the crash user documents are updated. The cache daemon is ignoring the database crash.
> The following patch updates the daemon to monitor the _users database and crash (letting the supervisor restart it) if the database process crashes.
> Etap test included.
> This might be related to COUCHDB-1212.

--
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