Keystone "user password set" should not require a scoped token

[Guang Yee]

Keystone V3 "user password set" is a self-service operation. It should not required a scoped token as it is not considered a "scoped operation."

To reproduce,

openstack --os-auth-url http://localhost:35357/v3 --os-username foo --os-password bar --os-user-domain-id default --os-identity-api-version 3 user password set
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

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/321985

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/321985
Committed: https://git.openstack.org/cgit/openstack/python-openstackclient/commit/?id=5f950788ffe528f509fe88c70179ec5e732bff82
Submitter: Jenkins
Branch: master

commit 5f950788ffe528f509fe88c70179ec5e732bff82
Author: Alvaro Lopez Garcia <email address hidden>
Date: Fri May 27 09:04:54 2016 +0200

    Do not require an scope when setting a password

    Changing the password in Keystone V3 is an unscoped operation, but we
    were requiring a scope.

    Change-Id: If0653ac7b59320c2cd9d42a2c73dd29c3626d389
    Closes-Bug: 1543222

[Doug Hellmann (doug-hellmann)]

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