Bug 1041947

Summary: [RFE][keystone]: Re-order terms in role assignment API URLs
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-ordering
Whiteboard: upstream_milestone_none upstream_status_unknown upstream_definition_obsolete
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 17:17:58 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 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