Bug 1043896

Summary: Create authorization for domain via rhc should allow using name instead of id only.
Product: OpenShift Online Reporter: Liang Xia <lxia>
Component: ocAssignee: Jordan Liggitt <jliggitt>
Status: CLOSED DUPLICATE QA Contact: libra bugs <libra-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.xCC: jliggitt, wsun
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-18 05:20:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Liang Xia 2013-12-17 12:19:14 UTC
Description of problem:
Currently, when we add authorizations for domain, we can only use id (domain/$domain_id/{admin,edit,view}.But we can not get domain id via rhc.
As domain name is also uniqe, we can allow using name to create authorizations (domain/$domain_name/{admin,edit,view}.

Version-Release number of selected component (if applicable):
devenv_4143
rhc 1.19.1

How reproducible:
always

Steps to Reproduce:
1.Try to create a domain token via rhc, found no way to get domain id via rhc.
2.
3.

Actual results:
No way to get domain id via rhc, while create authorizations for domain requires domain id.

Expected results:
Allow using domain name when create authorizations for domain.

Additional info:

Comment 1 Jordan Liggitt 2013-12-17 15:45:28 UTC
First step should be to expose the domain id via rhc. This involves bumping up the API version to 1.6, which we should probably do anyway.

Comment 2 Jordan Liggitt 2013-12-17 21:54:36 UTC
We don't want to allow scopes to use domain name, since domain names can change.

Comment 3 Wei Sun 2013-12-18 05:20:52 UTC
Seems this bug is duplicate with https://bugzilla.redhat.com/show_bug.cgi?id=1004709.

If they are not same,please re-open it.Thanks

*** This bug has been marked as a duplicate of bug 1004709 ***