Skip to content
This repository has been archived by the owner on Jan 13, 2022. It is now read-only.

Enable RBAC Visibility for End Users by Roles #66

Open
tomvachon opened this issue Nov 30, 2017 · 4 comments
Open

Enable RBAC Visibility for End Users by Roles #66

tomvachon opened this issue Nov 30, 2017 · 4 comments

Comments

@tomvachon
Copy link
Contributor

As an administrator of the system, I would like my end users to be limited in their visibility to the accounts which they are responsible for operating.

@markofu
Copy link
Contributor

markofu commented Dec 5, 2017

Hey @tomvachon,

I'm going to close this as this feature is already there. For example, in the Cloud Inquisitor UI:

  • go to Roles, create the role that you want, e.g. Account1 & save
  • go to Accounts, in Required Role (which is free-form) & add in the newly created role

I'm going to create a new feature to improve the workflow and documentation here. For example, one feature would be that the "required role" field auto-populates. See here.

@markofu markofu closed this as completed Dec 5, 2017
@tomvachon
Copy link
Contributor Author

@markofu I would argue this isn't an enhancement, this is a bug. RBAC isn't implemented if I can't block visibility. When they go to the front page, it errors our hard. They only way to fix that is to grant user, which grants view to all

@markofu
Copy link
Contributor

markofu commented Dec 7, 2017

Hey @tomvachon, ok that makes sense. I was not clear that, let's chat on Slack.

@markofu markofu reopened this Dec 7, 2017
@tomvachon
Copy link
Contributor Author

SO i think I have better info...

  1. RBAC only works if every account has required roles set. Otherwise they pop up for the end-user. This makes sense but isnt clear.

  2. RBAC is not applied into the reports views. I can see every single instance in Required Tags and Volume Audit; Instance Age does apply correct RBAC though

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants