Jump to: navigation, search

Difference between revisions of "DynamicPolicies"

(Roadmap)
(Roadmap)
Line 31: Line 31:
 
=== US 1 - As a cloud admin, I want to manage Policies via API ===
 
=== US 1 - As a cloud admin, I want to manage Policies via API ===
  
'''Depends On:''' None
+
'''Depends On:''' ''None''
 
<br />
 
<br />
  
Line 47: Line 47:
 
=== US 2 - As a cloud admin, I want to have services using the Policies I have defined via API ===
 
=== US 2 - As a cloud admin, I want to have services using the Policies I have defined via API ===
  
'''Depends On:''' US 1 - As a cloud admin, I want to manage Policies via API
+
'''Depends On:''' ''US 1 - As a cloud admin, I want to manage Policies via API''
 
<br />
 
<br />
 
   
 
   
Line 57: Line 57:
 
=== As a domain admin, I want to define roles that are meaningful to my business ===
 
=== As a domain admin, I want to define roles that are meaningful to my business ===
  
'''Depends On:''' None
+
'''Depends On:''' ''None''
 
<br />
 
<br />
  
Line 67: Line 67:
 
=== US 3 - As a user, I want to define role hierarchies, allowing one to only delegate a subset of her roles ===
 
=== US 3 - As a user, I want to define role hierarchies, allowing one to only delegate a subset of her roles ===
  
'''Depends On:''' None
+
'''Depends On:''' ''None''
 
<br />
 
<br />
  
Line 77: Line 77:
 
=== US 4 - As a deployer, I want to have better default policies, distinguishing different admin scopes ===
 
=== US 4 - As a deployer, I want to have better default policies, distinguishing different admin scopes ===
  
'''Depends On:''' US 3 - As a user, I want to define role hierarchies, allowing one to only delegate a subset of her roles
+
'''Depends On:''' ''US 3 - As a user, I want to define role hierarchies, allowing one to only delegate a subset of her roles''
 
<br />
 
<br />
  

Revision as of 13:33, 16 June 2015

Dynamic Policies

Improving Access Control on OpenStack


Weekly Meeting

TBD


Background

OpenStack uses a Role-Based Access Control mechanism to manage authorization, which defines if a user is able to perform actions on resources based on the roles he has assigned on them. Resources include VMs, volumes, networks, etc and are organized into projects, which are owned by domains. Users have roles assigned on domains or projects.

Users get domain or project scoped tokens, which contains the roles the user has assigned on them, and pass this token along to services in requests to perform actions on resources. The services check the roles and the scope from the token against the rules defined for the requested action on the policy.json file to determine if the user has enough privileges.


Evolution

  • How to evolve the policies management mechanism, which currently uses an out-of-band mechanism to update the policy.json files ?
  • How to improve delegation mechanism, allowing users to only delegate a subset of their roles, which may be customized per domain ?
  • How to provide better default policies, fixing the bug in which an admin anywhere is admin everywhere ?

Roadmap

US 1 - As a cloud admin, I want to manage Policies via API

Depends On: None

Description Bla ...


US 2 - As a cloud admin, I want to have services using the Policies I have defined via API

Depends On: US 1 - As a cloud admin, I want to manage Policies via API

Description Bla ...

As a domain admin, I want to define roles that are meaningful to my business

Depends On: None

Description Bla ...

US 3 - As a user, I want to define role hierarchies, allowing one to only delegate a subset of her roles

Depends On: None

Description Bla ...

US 4 - As a deployer, I want to have better default policies, distinguishing different admin scopes

Depends On: US 3 - As a user, I want to define role hierarchies, allowing one to only delegate a subset of her roles

Description Bla ...

  • Specs
    • Improve Default Policies
      • TODO: Create Spec