Bug 1041947 - [RFE][keystone]: Re-order terms in role assignment API URLs
Summary: [RFE][keystone]: Re-order terms in role assignment API URLs
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 20:14 UTC by RHOS Integration
Modified: 2015-07-22 17:59 UTC (History)
2 users (show)

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


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 20:14:00 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/keystone/+spec/role-assignment-ordering.

Description:

The v3 spec contains a series of URL APIs for role assignment management, e.g.:

PUT /domains/{domain_id}/users/{user_id}/roles/{role_id}

This seems an un-natural ordering, especially in the light of us wanting to define additional terms to indicate inheritance.  A more natural ordering within the url would be along the lines of how we describe a role assignment:

Create an assignment for "role X for User Y on Domain Z"

e.g. PUT /roles/{role_id}/users/{user_id}/domains/{domain_id}

It is proposed that we use this new ordering going forward, deprecate the old ordering (but of course continue to support this for a few releases)

Specification URL (additional information):

None


Note You need to log in before you can comment on or make changes to this bug.