Bug 1041883 - [RFE][keystone]: Make role-assignment a first class entity
Summary: [RFE][keystone]: Make role-assignment a first class entity
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/keys...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 19:52 UTC by RHOS Integration
Modified: 2016-02-03 05:05 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 17:18:36 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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
Note You need to log in before you can comment on or make changes to this bug.