auth_token requires v2.0 API

[Dolph Mathews]

I did a v3-only deploy of keystone [1] to see what would break, and it turns out that auth_token is still hardcoded to make v2.0 calls, even if you explicitly set the 'auth_version' to 'v3.0'. Keystone produces error logs like this:

  "POST /v2.0/tokens HTTP/1.1" 404 260 "-" "python-requests/2.2.1 CPython/2.7.3 Linux/3.2.0-4-amd64"
  "GET /v2.0/tokens/revoked HTTP/1.1" 404 260 "-" "python-requests/2.2.1 CPython/2.7.3 Linux/3.2.0-4-amd64"

Both 404's are a result of /v2.0/ simply not being available. For example, GET / on keystone looks like this:

  {"versions": {"values": [{"status": "stable", "updated": "2013-03-06T00:00:00Z", "media-types": [{"base": "application/json", "type": "application/vnd.openstack.identity-v3+json"}, {"base": "application/xml", "type": "application/vnd.openstack.identity-v3+xml"}], "id": "v3.0", "links": [{"href": "http://192.168.111.222:35357/v3/", "rel": "self"}]}]}}

The _request_admin_token() method [2] and fetch_revocation_list() method are both hardcoded to call /v2.0/

[1] https://github.com/dolph/keystone-deploy
[2] https://github.com/openstack/python-keystoneclient/blob/master/keystoneclient/middleware/auth_token.py#L777-L816
[3] https://github.com/openstack/python-keystoneclient/blob/master/keystoneclient/middleware/auth_token.py#L1351-L1366

[Dolph Mathews (dolph)]

Given that v2.0 is now deprecated, getting auth_token off of v2.0 should be high priority.

[Jamie Lennox (jamielennox)]

Yes, that's a long standing one. The discovery and client changes i've got proposed are working towards this somewhat indirectly.

[OpenStack Infra (hudson-openstack)]

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