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

Rework permission scheme (authorization) #188

Open
15 tasks
FRosner opened this issue Nov 28, 2016 · 0 comments
Open
15 tasks

Rework permission scheme (authorization) #188

FRosner opened this issue Nov 28, 2016 · 0 comments
Labels
Milestone

Comments

@FRosner
Copy link
Owner

FRosner commented Nov 28, 2016

Problem

Currently you have predefined roles (admin, operator, user) and also the instance regex. Also, one user can only have one of each.

Solution

Make permission scheme more modular.

  • A user belongs to one or multiple groups
  • A group has no or multiple permissions assigned
  • Permission types are predefined, but each permission might be associated with additional information when assigned to a group (e.g. the instance / template filter through regex)
  • Regexes are defined by the user and are reusable (Are they maybe better handled through input validation based on groups Input validation #199?)

Also we should give a usable example (ship it with the dist?)

  • Admin group
  • Operator group
  • User group

Permissions

Parameter arguments should be optional if possible with a sane default (e.g. no filter). Filters should be implemented to be as flexible as possible (e.g. regex).

  • create instance (instance filter, template filter)
  • edit instance (instance filter, template filter, parameter filter)
  • delete instance (instance filter, template filter)
  • update instance (instance filter, template filter)
  • view instance (instance filter, template filter)
  • view template (template filter)
  • start/resubmit instance (instance filter, template filter)
  • stop instance (instance filter, template filter)
@FRosner FRosner added this to the 1.0.0 milestone Nov 28, 2016
@FRosner FRosner modified the milestones: 0.7.0, 1.0.0 Jun 4, 2017
@FRosner FRosner modified the milestones: 0.7.0, 1.0.0 Aug 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant