-
Notifications
You must be signed in to change notification settings - Fork 35
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
Allow only administrators to add APIs to a deployment #1616
Comments
@frenchbread Would you be interested in this task? |
@bajiat self-assigned |
@frenchbread : (from rocket chat, based on your sample wireframe) Rename the header as "Access to API" I think that in upcoming times, there would be other access privileges specific to roles. |
@frenchbread wireframes added as you suggested. |
@Nazarah Let's keep this simple for starters. So let's only do the simple setting now (first wireframe). I would rename it: "Access to API" to "Adding APIs" or "Publishing APIs" The second wireframe we would consider later. For clarity, I would not include it in this issue. (Also, I do not understand the combination "Adding an API" and Read privilege.) |
The point to limit that anyone can't add any kind of API can be in other way also: To limit only Admin to be able to add API.
Definition of done
Wireframe
One more suggestion if there are future needs to implement more privileges based on user roles.
There can be a separate module named "User Role and Privileges"
This view would contain access privileges to different APINF users (Admin, API Owner, API Consumer) as radio buttons.
N - non accessible
R - Only view mode
W - View and Edit
Once a new privilege is introduced, this can be added in all three role panes.
The text was updated successfully, but these errors were encountered: