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

feat: add access control #43

Open
alohamora opened this issue Nov 1, 2023 · 0 comments · May be fixed by #44
Open

feat: add access control #43

alohamora opened this issue Nov 1, 2023 · 0 comments · May be fixed by #44

Comments

@alohamora
Copy link
Contributor

Add access control configuration to restrict the permissions over the following methods

  1. All GET endpoints, as well as the POST /services endpoint should be accessible to every authenticated user, that is, no specific access policies apply.
  2. Users who post a new service become their Owner. Owners can set the roles for other users, to Owner or Maintainer, for that particular resource. They can also DELETE and edit (PUT) services.
  3. Maintainers can only edit (PUT) services, but not delete or set roles for other users.
  4. Admins of the service are the only ones who can use the POST service-info/ endpoint and give other users Admin permissions. One or more Admins should be configured when a service is initially deployed (probably via the config). Admins can not modify or delete services or set Owner or Maintainer permissions for services that they do not own, so the Admin role is really restricted to setting the service info of the registry itself.
@alohamora alohamora linked a pull request Nov 1, 2023 that will close this issue
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant