python-openstackclient/releasenotes/notes/bug-1592062-e327a31a5ae66809.yaml
Dolph Mathews fe0c8e955b Do not prompt for scope options with default scoped tokens
This changes the scope validation to occur after a token has already
been created.

Previous flow:

1. Validate authentication options.
2. Validate authorization options if the command requires a scope.
3. Create a token (using authentication + authorization options)
4. Run command.

This means that scope was being checked, even if a default scope was
applied in step 3 by Keystone.

New flow:

1. Validate authentication options.
2. Create token (using authentication + authorization options)
3  Validate authorization options if the command requires a scope and
   the token is not scoped.
4. Run command.

Change-Id: Idae368a11249f425b14b891fc68b4176e2b3e981
Closes-Bug: 1592062
2016-06-17 12:37:15 -04:00

6 lines
203 B
YAML

---
fixes:
- Scope options are now validated after authentication occurs, and only if
the user does not have a default project scope.
[Bug `1592062 <https://bugs.launchpad.net/bugs/1592062>`_]