For explicit unscoped authentication, the keystome server
specifies the scope parameter value as 'unscoped'. However
keystoneauth1 initialises it to {'unscoped': {}}. This
patch removes this inconsistency.
Updated the corresponding test for unscoped request which
checks the scope parameter in auth to match the 'unscoped'
string.
Reviewed: https:/ /review. openstack. org/452652 /git.openstack. org/cgit/ openstack/ keystoneauth/ commit/ ?id=d0cdc355a4f 7a4fcb03c65b899 4de436f4b00a52
Committed: https:/
Submitter: Jenkins
Branch: master
commit d0cdc355a4f7a4f cb03c65b8994de4 36f4b00a52
Author: Samriddhi <email address hidden>
Date: Mon Apr 3 14:42:37 2017 +0530
Updated inconsistent value of scope parameter
For explicit unscoped authentication, the keystome server
specifies the scope parameter value as 'unscoped'. However
keystoneauth1 initialises it to {'unscoped': {}}. This
patch removes this inconsistency.
Updated the corresponding test for unscoped request which
checks the scope parameter in auth to match the 'unscoped'
string.
Partial-Bug #1637682
Change-Id: I1c9d89fd86773f 4acecbefcdad4dc a6cff16b58d