Skip to content
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

Closed
4 tasks done
bajiat opened this issue Sep 23, 2016 · 5 comments
Closed
4 tasks done

Allow only administrators to add APIs to a deployment #1616

bajiat opened this issue Sep 23, 2016 · 5 comments
Assignees
Milestone

Comments

@bajiat
Copy link
Contributor

bajiat commented Sep 23, 2016

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

  • There is a setting where admins can select that only admins can add APIs in this deployment.
  • When admin has selected this admin only setting
    • The link to Add API is not visible to other type of users than admins.
    • Other users than admins don't have insert privileges on the APIs collection.

Wireframe

addapiadminprivilege

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.

addapiadminprivilege2

@bajiat bajiat changed the title Allow only administrators to add APIs to one deployment Allow only administrators to add APIs to a deployment Sep 23, 2016
@bajiat
Copy link
Contributor Author

bajiat commented Sep 26, 2016

@frenchbread Would you be interested in this task?

@frenchbread frenchbread self-assigned this Sep 26, 2016
@frenchbread
Copy link
Contributor

@bajiat self-assigned

@Nazarah
Copy link
Contributor

Nazarah commented Sep 26, 2016

@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.
So should any privilege for a role can be selected with radio buttons? with N - NONE, R - READ and W - WRITE accesses?
this could be added as a separate view called Role Privileges under Settings

@Nazarah
Copy link
Contributor

Nazarah commented Sep 27, 2016

@frenchbread wireframes added as you suggested.
Also added the wireframe to arrange privileges specific to user roles.

@bajiat
Copy link
Contributor Author

bajiat commented Sep 27, 2016

@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.)

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

No branches or pull requests

4 participants