e420b16c22
In be558717 the request handling was refactored and more of the token handling was left to keystonemiddleware. However, when using the deprecated admin_token, the token needs to be handled differently. Specifically, there may be no 'token' or 'access' key in the body of the request, which keystoneauth expects to have keystonemiddleware pass to it[1][2]. Luckily the admin_token doesn't need a lot of special processing, so we can just skip that step and move on to fill_context. [1] http://git.openstack.org/cgit/openstack/keystonemiddleware/tree/keystonemiddleware/auth_token/__init__.py#n399 [2] http://git.openstack.org/cgit/openstack/keystoneauth/tree/keystoneauth1/access/access.py#n41 Closes-bug: #1603038 Change-Id: Iac4a5769072925fe2f36768c8f31816e6866f2f6
OpenStack Keystone
Keystone provides authentication, authorization and service discovery mechanisms via HTTP primarily for use by projects in the OpenStack family. It is most commonly deployed as an HTTP interface to existing identity systems, such as LDAP.
Developer documentation, the source of which is in
doc/source/, is published at:
The API specification and documentation are available at:
The canonical client library is available at:
https://git.openstack.org/cgit/openstack/python-keystoneclient
Documentation for cloud administrators is available at:
The source of documentation for cloud administrators is available at:
Information about our team meeting is available at:
Bugs and feature requests are tracked on Launchpad at:
Future design work is tracked at:
http://specs.openstack.org/openstack/keystone-specs/#identity-program-specifications
Contributors are encouraged to join IRC
(#openstack-keystone on freenode):
For information on contributing to Keystone, see
CONTRIBUTING.rst.