[
https://issues.apache.org/jira/browse/COUCHDB-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672553#comment-13672553
]
Robert Newson commented on COUCHDB-1818:
----------------------------------------
Could you define "it can cause issues with futon and the REST API."?
Deleting any config property gives this behavior. A deleted property will
return the atom 'undefined' in code, which is distinct from any actual value.
What bug are you reporting?
> Deleting Admin using REST API does not completely delete the admin in the
> local.ini file
> ----------------------------------------------------------------------------------------
>
> Key: COUCHDB-1818
> URL: https://issues.apache.org/jira/browse/COUCHDB-1818
> 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: http://www.atlassian.com/software/jira
