couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Bluhm (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1818) Deleting Admin using REST API does not completely delete the admin in the local.ini file
Date Sun, 02 Jun 2013 17:32:20 GMT


Todd Bluhm commented on COUCHDB-1818:

The issues it was causing with futon was an in ability to delete or create dbs. Going into
a db and clicking delete would not delete the db. If I performed a server restart it would
fix the issue. I came across this issue after running a test suite for a web framework I was
working on. The tests repeatedly added and delete an admin for each test (about 6 tests).
So it may be a bug with repetition rather than single use. As for how the config file deletes
properties, I was not aware that was how it occurred, so when I saw the "TestAdmin= " I incorrectly
assumed that was the issue. I filed a bug just in case anyone else ran into a similar issue.
> Deleting Admin using REST API does not completely delete the admin in the local.ini file
> ----------------------------------------------------------------------------------------
>                 Key: COUCHDB-1818
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: HTTP Interface, Infrastructure
>            Reporter: Todd Bluhm
> Using Couchdb 1.3
> When using the REST API to delete an admin user that was inserted using the REST API,
only that admin's password is deleted from the local.ini file, while the admin's username
remains under the [admins] section of the local.ini file.
> Steps to Reproduce:
> 1. System in Admin Party mode.
> 2. User creates admin using REST API (PUT _config/admins/TestAdmin)
> 3. User deletes admin using REST API (DELETE _config/admins/TestAdmin)
> 4. Inspect the local.ini file and notice under [admins]: "TestAdmin = "
> Results:
> If in admin party mode afterwards, it can cause issues with futon and the REST API.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message