dd70a5548e
The V3 routes were being added by the append_v3_routers function in each controller package, so the only way state could be stored is in a global variable which makes unit testing difficult. With this change, the append_v3_routers functions are put into a class in each package. This will eventually be used to store JSON Home data. bp json-home Change-Id: I744a4c82dc84bb1a8d29d0314e3c51cc43c077a2 |
||
---|---|---|
bin | ||
doc | ||
etc | ||
examples/pki | ||
httpd | ||
keystone | ||
rally-scenarios | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.testr.conf | ||
babel.cfg | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
MANIFEST.in | ||
openstack-common.conf | ||
README.rst | ||
requirements-py3.txt | ||
requirements.txt | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements-py3.txt | ||
test-requirements.txt | ||
tox.ini |
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 is available at:
The API documentation is 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:
Bugs and feature requests are tracked on Launchpad at:
Future design work is tracked at:
Contributors are encouraged to join IRC
(#openstack-keystone
on freenode):
For information on contributing to Keystone, see
CONTRIBUTING.rst
.