-
Notifications
You must be signed in to change notification settings - Fork 429
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API Token Management #910
Comments
The first step here is to create a 'Role' entity which can then be attached to a User, Group or an API token. |
@kyle-ssg one thing that we've discussed as part of this is having a single view of the permissions across all entities for a Role (which we can extend to use for Users / Groups too). So we would need a panel for Org, Projects (with a drop down to select the project perhaps?), Environments (with a drop down to select the env perhaps?). Does that sound feasible? |
Since we don't want the tokens to be associated with the user, we have ruled out using There are a couple of things we can do here:
I am leaning more towards 2(i) |
Agree with 2 |
Yep, also agree with 2(i) |
The backed part of roles was added here: #2232 |
As per our conversation in this regard, I will first create a couple of UI/UX designs for Role management at the Organisation Management level either in a new |
@matthewelwell @kyle-ssg here are the UI designs for roles management: |
Needs FE work still. |
At the moment, to use the rest API, user's must use an API token associated with a user. We should add the ability to create API tokens scoped to allow access to the relevant resources.
The text was updated successfully, but these errors were encountered: