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

TO API - should not be able to create / update a user with a higher role than your role #875

Closed
mitchell852 opened this issue Aug 29, 2017 · 0 comments · Fixed by #1170
Closed
Assignees
Labels
Traffic Ops related to Traffic Ops
Milestone

Comments

@mitchell852
Copy link
Member

Currently, to create or update a user thru the TO API, you have to have the admin or operations role, however, going forward your role will not dictate your ability to create/update users but rather the capabilities attached to your role.

Going forward roles can be arbitrarily created and attached to whatever capabilities the administration of the system desires.

For example, roles could look like this:

  • admin (all capabilities)
  • operations (whatever capabilities make sense for this role)
  • foo (whatever capabilities make sense for this role)
  • bar (whatever capabilities make sense for this role)
  • read-only (whatever capabilities make sense for this role)
  • disallowed (no capabilities)

In this example, if the foo role has the user-write capability, anyone with the foo role can create or update users which means they could create a user and give them the admin role and thus sidestepping roles/capabilities altogether.

When creating / updating users, you should never be able to assign a role with a higher priv level than your role's priv level.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Traffic Ops related to Traffic Ops
Projects
None yet
1 participant