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.
Reviewed: https:/ /review. openstack. org/330057 /git.openstack. org/cgit/ openstack/ python- openstackclient /commit/ ?id=fe0c8e955be 0331aef9cc6847c 9bddc43ce66d92
Committed: https:/
Submitter: Jenkins
Branch: master
commit fe0c8e955be0331 aef9cc6847c9bdd c43ce66d92
Author: Dolph Mathews <email address hidden>
Date: Wed Jun 15 16:26:35 2016 +0000
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: Idae368a11249f4 25b14b891fc68b4 176e2b3e981
Closes-Bug: 1592062