
Official recommendation for operators is to develop out-of-tree drivers for the missing functionality. While this is easily possible there are hurdles for configuring such drivers. Configuring them using FS requires restart of Keystone when i.e. adding new domains to be processed with the custom driver. Using database is a much better and dynamical approach, but it currently is not allowing drivers to have specific configuration. This change improves this flaws and contains of 3 individual parts that are submitted together to make testing easier. - Allowing driver to register supported configuration option before loading the driver (invoke DriverManager without calling the driver and search for specific method present). - Allow changing driver specific configuration through API (add 2 more configuration options enabling listed options in the API) - Documentation changes. Change-Id: I99fa798ef60cdb7a488fe55de76cd931c6db3e89
OpenStack Keystone
OpenStack 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 reference and documentation are available at:
The canonical client library is available at:
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:
Release notes is available at:
Bugs and feature requests are tracked on Launchpad at:
Future design work is tracked at:
Contributors are encouraged to join IRC
(#openstack-keystone
on OFTC):
Source for the project:
For information on contributing to Keystone, see
CONTRIBUTING.rst
.