Keystone "token issue" command should support unscoped token

Bug #1543214 reported by Guang Yee on 2016-02-08
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released
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"

Steve Martinelli (stevemar) wrote :
Changed in python-openstackclient:
assignee: nobody → Guang Yee (guang-yee)
importance: Undecided → Medium
status: New → In Progress

Submitter: Jenkins
Branch: master

commit 41e1bd0be64e15a5e0c12b45bdf3dcde5fabf244
Author: guang-yee <email address hidden>
Date: Mon Feb 8 11:16:24 2016 -0800

    Support unscoped token request

    Make scope check optional for the "token issue" command as unscoped token is
    a valid Keystone V2/V3 API.

    Change-Id: Ie1cded4dbfdafd3a78c0ebdf89e3f66762509930
    Closes-Bug: #1543214

Changed in python-openstackclient:
status: In Progress → Fix Released

This issue was fixed in the openstack/python-openstackclient 2.2.0 release.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers