wohali opened a new issue #929: db security form does not populate with 
existing object,
URL: https://github.com/apache/couchdb-fauxton/issues/929
 
 
   ## Expected Behavior
   When browsing to `http://<url>/_utils/#/database/dbname/permissions` , the 
page should reflect the content of the current database `_security` object. It 
should then allow incremental editing of the object through adding/deleting 
admin and member users and roles.
   
   ## Current Behaviour
   When browsing to `http://<url>/_utils/#/database/dbname/permissions` , the 
page currently shows no data, as if there was no `_security` object in the 
database.
   
   ## Steps to Reproduce
   1. `curl -X PUT http://<url>/dbname`
   2. Create a user such as `wohali` in `_users` and make it an admin (e.g. by 
adding it to `[admins]` in local.ini
   3. `curl -X PUT http://wohali:password@<url>/dbname/_security -d '{"admins": 
{"names": [ "wohali" ], "roles": ["foo", "bar"]}, "members": { "names": 
["ralph","frank"], "roles":["developers"]}}'` to create the correct db 
permissions.
   4. `curl -X GET http://wohali:password@<url>/dbname/_security` and validate 
the output
   4. Visit `https://<url>/_utils/#/database/dbname/permissions`. None of the 
populated data in the `_security` object is shown. 
   
   **Note**: in my browser network console the `GET /_security` on that page 
returns a 401 error. Inspecting the headers for the request does not show the 
request being made with the correct security context.
   
   ## Your Environment
   * Version used: CouchDB, master build
   * Browser Name and version: Firefox 53.0.3
   * Operating System and version (desktop or mobile): Windows 7 x64, desktop
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to