Colleen Murphy 86428a6c66 Delete shadow users when domain is deleted ... Without this change, when an admin tries to delete an LDAP-backed domain, it fails due to the foreign key relationship in the users table. Previously, we were assuming that LDAP users existed solely in the LDAP directory, but this is not true with shadow users. This patch fixes the logic to delete the shadow users upon domain deletion. Change-Id: I12a08001e3aa08e4db9438cae425ad1a0a8070f7 Closes-bug: #1801873 (cherry picked from commit 1b16725d06)		2019-04-02 15:46:46 +00:00
..
backends	LDAP attribute names non-case-sensitive	2018-10-02 14:14:00 +00:00
id_generators	Replace six iteration methods with standard ones	2016-09-08 18:56:31 +08:00
mapping_backends	Remove Dependency Injection	2017-12-13 10:59:39 -08:00
shadow_backends	Delete shadow users when domain is deleted	2019-04-02 15:46:46 +00:00
__init__.py	Remove exposure of routers at package level	2015-12-03 15:06:56 -03:00
controllers.py	Use keystone.common.provider_api for identity APIs	2017-12-27 18:44:06 +00:00
core.py	Delete shadow users when domain is deleted	2019-04-02 15:46:46 +00:00
generator.py	Remove Dependency Injection	2017-12-13 10:59:39 -08:00
routers.py	Remove v2.0 identity APIs	2017-09-29 20:42:12 +00:00
schema.py	Remove v2 schema and validation tests	2017-10-19 17:20:47 -05:00