keystone/keystone/identity
Henry Nash 8e6e6b392c Ensure identity sql driver supports domain-specific configuration.
For an identity driver to be used with a domain-specific config file,
it must accept a ConfigOpts as an optional parameter. The ldap driver
already supported this - so this patch adds this to the sql driver.

The above change is trivial, but the rest of the patch is enhancing
our testing to validate this operation, as well as enforcing the
limitation listed below.

Limitation:

Currently Keystone only supports one SQL driver - this patch
does not change that.  What it does enable is for that one SQL
driver to be assigned to a specific domain, as opposed to being just
a catch-all for domains without a specific configuration file.
This at least enables the (often requested) scenario of service users
to be stored in SQL in a predominantly LDAP installation.

Closes-Bug: 1217017
Change-Id: Ic531ebae28680fc518d8e036db516f5982241c40
2014-09-18 10:17:23 +01:00
..
backends Ensure identity sql driver supports domain-specific configuration. 2014-09-18 10:17:23 +01:00
id_generators Add identity mapping capability 2014-07-02 11:29:07 +01:00
mapping_backends Avoid loading a ref from SQL to delete the ref 2014-07-11 19:43:36 +00:00
__init__.py Add identity mapping capability 2014-07-02 11:29:07 +01:00
controllers.py Use oslo.i18n 2014-07-13 10:29:41 -05:00
core.py Ensure identity sql driver supports domain-specific configuration. 2014-09-18 10:17:23 +01:00
generator.py correct typos 2014-09-08 12:29:25 -05:00
routers.py Change the sub-routers to provide JSON Home data 2014-08-26 09:57:15 -05:00