Bug 1152989 – [RFE] Allow use of role names in api definitions

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1152989 - [RFE] Allow use of role names in api definitions

Summary:	[RFE] Allow use of role names in api definitions

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Virtualization Manager
Classification:	Red Hat
Component:	ovirt-engine (Show other bugs)
Sub Component:
Version:	3.4.0
Hardware:	x86_64 Linux

Priority	medium Severity medium
Target Milestone:	ovirt-3.6.0-rc
Target Release:	3.6.0
Assigned To:	Juan Hernández
QA Contact:	Antonin Pagac
Docs Contact:

URL:
Whiteboard:
Keywords:	FutureFeature

Depends On:
Blocks:	1219829 1219831
	Show dependency tree / graph

Reported:	2014-10-15 06:43 EDT by Prasad Mukhedkar
Modified:	2016-03-09 15:41 EST (History)
CC List:	14 users (show)

See Also:
Fixed In Version:
Doc Type:	Enhancement
Doc Text:	Previously, when adding a permission via the REST API the user had to specify the role identifier and not the role name. This meant that the user needed to look up the identifier, issuing an additional call to the top level 'roles' collection. Roles have human readable names, such as UserVmManager, but the REST API did not support specifying these names. Now, the REST API supports both ways to specify a role. This is also supported by the Python SDK, the Java SDK, and the RHEVM Shell.
Story Points:	---
Clone Of:
Clones:	1219829 1219831 (view as bug list)
Environment:
Last Closed:	2016-03-09 15:41:17 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	Infra
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Flags:	sherold: Triaged+

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

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
oVirt gerrit	40694	master	MERGED	core, restapi: Support adding permission using role name	Never
Red Hat Product Errata	RHEA-2016:0376	normal	SHIPPED_LIVE	Red Hat Enterprise Virtualization Manager 3.6.0	2016-03-09 20:20:52 EST

Groups: None (edit)

Description Prasad Mukhedkar 2014-10-15 06:43:06 EDT

Description of problem:

Currently, If we want to add the role "UserVmManager" to a group we need to get the Id of that role first.

Current API:

<permission>
    <role id="00000000-0000-0000-0000-000000000001" />
    <group id="abee5751-3857-46dd-abaa-03f57bca2e86"/>
</permission>

I would like to directly use the role name:

<permission>
    <role><name>UserVmManager</name></role>
    <group id="abee5751-3857-46dd-abaa-03f57bca2e86"/>
</permission>

with most other resource references this already works, For example,
network can be referenced by id or by name: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.4/html-single/Technical_Guide/index.html#sect-Networks_Sub-Collection

why not roles than?

Comment 4 Max Kovgan 2015-06-28 10:12:07 EDT

ovirt-3.6.0-3 release

Comment 5 Antonin Pagac 2015-07-02 06:22:39 EDT

Verified in: ovirt-engine-restapi-3.6.0-0.0.master.20150627185750.git6f063c1.el6.noarch

Comment 8 errata-xmlrpc 2016-03-09 15:41:17 EST

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-0376.html

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