Bug 1152989
Summary: | [RFE] Allow use of role names in api definitions | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Prasad Mukhedkar <pmukhedk> | |
Component: | ovirt-engine | Assignee: | Juan Hernández <juan.hernandez> | |
Status: | CLOSED ERRATA | QA Contact: | Antonin Pagac <apagac> | |
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | 3.4.0 | CC: | bazulay, gassmann, iheim, juan.hernandez, lsurette, melewis, oourfali, rbalakri, Rhev-m-bugs, sherold, yeylon, ykaul, ylavi | |
Target Milestone: | ovirt-3.6.0-rc | Keywords: | FutureFeature | |
Target Release: | 3.6.0 | Flags: | sherold:
Triaged+
|
|
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
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: | ||||
: | 1219829 1219831 (view as bug list) | Environment: | ||
Last Closed: | 2016-03-09 20:41:17 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1219829, 1219831 |
Description
Prasad Mukhedkar
2014-10-15 10:43:06 UTC
ovirt-3.6.0-3 release Verified in: ovirt-engine-restapi-3.6.0-0.0.master.20150627185750.git6f063c1.el6.noarch 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 |