When auth_version is set to be v3.0 in glance-api.conf, I see this in the logs "Auth Token proceeding with requested v3.0 apis" but in the very next debug log I see that the authentication request actually appends v2.0 to the identity url, which seems incorrect.
2015-03-31 00:52:13.928 254 INFO keystonemiddleware.auth_token [-] Auth Token proceeding with requested v3.0 apis
2015-03-31 00:52:13.928 254 DEBUG keystoneclient.auth.identity.v2 [-] Making authentication request to https://<keystone server>:35357/v2.0/tokens get_auth_ref /usr/lib/python2.7/site-packages/keystoneclient/auth/identity/v2.py:76
When auth_version is set to be v3.0 in glance-api.conf, I see this in the logs "Auth Token proceeding with requested v3.0 apis" but in the very next debug log I see that the authentication request actually appends v2.0 to the identity url, which seems incorrect.
2015-03-31 00:52:13.928 254 INFO keystonemiddlew are.auth_ token [-] Auth Token proceeding with requested v3.0 apis auth.identity. v2 [-] Making authentication request to https://<keystone server> :35357/ v2.0/tokens get_auth_ref /usr/lib/ python2. 7/site- packages/ keystoneclient/ auth/identity/ v2.py:76
2015-03-31 00:52:13.928 254 DEBUG keystoneclient.
Relevant config from glance-api.conf:
[keystone_ authtoken]
identity_uri = https://<keystone server>:35357
admin_user = glance
admin_password =<admin_password>
auth_version = v3.0