yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #35617
[Bug 968696] Re: "admin"-ness not properly scoped
** Changed in: nova
Status: Fix Released => Confirmed
** Changed in: nova
Milestone: 2012.2 => None
** Changed in: nova
Assignee: Jake Dahn (jakedahn) => (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/968696
Title:
"admin"-ness not properly scoped
Status in OpenStack Dashboard (Horizon):
Fix Released
Status in Keystone:
Confirmed
Status in neutron:
Incomplete
Status in OpenStack Compute (nova):
Confirmed
Bug description:
Fact: Keystone's rbac model grants roles to users on specific tenants,
and post-keystone redux, there are no longer "global" roles.
Problem: Granting a user an "admin" role on ANY tenant grants them
unlimited "admin"-ness throughout the system because there is no
differentiation between a scoped "admin"-ness and a global
"admin"-ness.
I don't have a specific solution to advocate, but being an admin on
*any* tenant simply *cannot* allow you to administer all of keystone.
Steps to reproduce (from Horizon, though you could do this with the
CLI, too):
1. User A (existing admin) creates Project B and User B.
2. User A adds User B to Project B with the admin role on Project B.
3. User B logs in and now has unlimited admin rights not only to view things in the dashboard, but to take actions like creating new projects and users, managing existing projects and users, etc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/968696/+subscriptions