Open dmitrizagidulin opened 9 years ago
Pretty sure we said this is Step 3 in the discussion doc which makes it after the Q2 release, no?
Ah, no, this is just to be able to use our current functionality (browse / edit objects) for nodes that have Authz enabled.
We may be able to get away with not implementing this until later, if we implement #91 (the ability to run Explorer in HTTPS mode).
To support the use case of customers using Riak Authz users for their dev teams, Explorer itself needs to be able to have its own user, to perform various riak api actions (browse stats, list buckets, etc). This especially becomes important when Dev Mode is off, and Explorer is being used (in a limited fashion) in production. So:
/riak/
api calls.Note: This is to support the per-app user only, with broad permissions. The ability for individual developers to log in with their own users, and only show those buckets they have permissions for, is separate.