Keystone "token issue" command should support unscoped token
Bug #1543214 reported by
Guang Yee
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-openstackclient |
Fix Released
|
Medium
|
Guang Yee |
Bug Description
Looks like OpenStack CLI required a scoped token regardless. There are instance where a scoped token is not required. (i.e. list projects I have access to, email update, etc). At the very least, for API completeness, "token issue" should support unscoped tokens
To reproduce, run "token issue" without specifying a scope and you'll get an error like this.
"Missing parameter(s):
Set a scope, such as a project or domain, set a project scope with --os-project-name, OS_PROJECT_NAME or auth.project_name, set a domain scope with --os-domain-name, OS_DOMAIN_NAME or auth.domain_name"
To post a comment you must log in.
patch is up: https:/ /review. openstack. org/#/c/ 277563/ 3