couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Filipe Manana (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (COUCHDB-1357) Authentication failure after updating password in user document
Date Sat, 10 Dec 2011 21:10:40 GMT

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

Filipe Manana updated COUCHDB-1357:
-----------------------------------

    Attachment: 0001-Clear-credentials-cache-if-_users-db-crashes.patch

Updated patch to deal with the case where the auth database is modified during run time. When
this happens the new database process most be monitored.
Also updated the tests to be more comprehensive. 
                
> 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: 0001-Clear-credentials-cache-if-_users-db-crashes.patch, 0001-Let-the-credentials-cache-daemon-crash-if-_users-db-.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

        

Mime
View raw message