Closed Toshbrown closed 6 years ago
That shouldn't be a problem to add.
arguably this is an example of the sort of audit functionality that we want to start building -- consuming the audit info to determine not just which app has which permission, but perhaps also when granted, timeline of evolution of what was granted, etc.
seems preferable to support like that i think, rather than add a special-case endpoint?
On Wed, 27 Jun 2018 at 17:50, John Moore notifications@github.com wrote:
That shouldn't be a problem to add.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/me-box/databox/issues/269#issuecomment-400751374, or mute the thread https://github.com/notifications/unsubscribe-auth/AAKP4FK-nb61-lxPC0VmuZWWKyq-cvedks5uA7fUgaJpZM4U6BJA .
-- Richard Mortier mort@cantab.net
Once the current version of the arbiter is in I plan to add the same audit support that exists on stores so you can OBSERVE this type of information over the middleware.
This sounds like a better way to proceed. Closing this issue as its no longer needed.
The old arbiter offered a UI over https that listed the currently granted permissions for each databox component. The new arbiter does not offer this functionality.
While not essential it was useful for debugging and I can envisage it being useful in other places (a screen the shows what apps have access to what data sources for example).
Can we add a new endpoint to the arbiter that returns all the currently granted permissions as a JSON object? This could then be rendered by the container manager UI into something useful for users and devs.
@jptmoore @mor1 any thoughts?