Bug 1041883

Summary: [RFE][keystone]: Make role-assignment a first class entity
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/keystone/+spec/role-assignment-crud
Whiteboard: upstream_milestone_none upstream_status_not-started upstream_definition_obsolete
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 17:18:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-12 19:52:44 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/keystone/+spec/role-assignment-crud.

Description:

In Havana, we introduced the GET /role-assignment API, but deferred its promotion to a first class entity with full crud access.  This would replace the existing grant crud of, e.g., DELETE /users/{user_id}/projects/{project_id}/roles/{role_id}.  These would, of course, still be supported, but marked as depreciated.

Specification URL (additional information):

None