mikerhodes commented on issue #1504: Redesign CouchDB security system URL: https://github.com/apache/couchdb/issues/1504#issuecomment-415074692 Mostly, for me, there are a few things that [our IAM implementation](https://console.bluemix.net/docs/services/Cloudant/guides/iam.html) does which would be really nice: - Convert a request (based on request path) to a symbolic action name which can then be used for authz and for request dispatching within the system (rather than having various places parsing URL paths etc.). E.g., `couchdb.db.read-document`. - There is a flexible actions to roles mapping that can be set up by an admin -- so we'd be able to allow a couch admin to create and "operator" role and specify what that role has access to (e.g., the various `_info` endpoints, things under `/_admin` and so on). - Likely the `_security` doc format needs to be altered to allow for a more flexible role/user/group mappings. I like the idea of chttpd converting the HTTP request into some kind of object that's specific to the request being made, like a view request, and validating all the parameters when creating that request-specific object, rather than passing down the HTTP request itself. I think this would be needed to really have a solid security split, as the lower levels could assume both the request is allowed and that the data can be trusted.
---------------------------------------------------------------- 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
