The v2.0 API spec uses username for the user's name, whereas the v3 API
just uses name. The v2.0 implementaion incorrectly used name instead of
username, but did allow a username to be specified and stored in the
extras.
This patch makes the implementation more closely conform to the API
without breaking backward compatibility. Anyone using name in the v2.0
API can continue to do so. They can even specify a username that will
still get stored in the extras. Users can now use the documented
username instead of name and the API will work for them as well.
Both name and username will always be returned for the v2 API calls.
Reviewed: https:/ /review. openstack. org/48342 /git.openstack. org/cgit/ openstack/ keystone/ commit/ ?id=6f8bdae1dbe 19eb3eb346fb696 506b4390f320fb
Committed: https:/
Submitter: Jenkins
Branch: master
commit 6f8bdae1dbe19eb 3eb346fb696506b 4390f320fb
Author: David Stanek <email address hidden>
Date: Wed Sep 25 13:29:33 2013 +0000
Adds support for username to match the v2 spec
The v2.0 API spec uses username for the user's name, whereas the v3 API
just uses name. The v2.0 implementaion incorrectly used name instead of
username, but did allow a username to be specified and stored in the
extras.
This patch makes the implementation more closely conform to the API
without breaking backward compatibility. Anyone using name in the v2.0
API can continue to do so. They can even specify a username that will
still get stored in the extras. Users can now use the documented
username instead of name and the API will work for them as well.
Both name and username will always be returned for the v2 API calls.
DocImpact 1925399fa59e502 2d31f68d374
Change-Id: Ia95aa5d442a831
Closes-Bug: #1214686