keystone/keystone/identity
Colleen Murphy d76a068d13 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.

Altered cherry-pick: use injected API provider since provider_api
mechanism doesn't exist in pike.

Change-Id: I12a08001e3aa08e4db9438cae425ad1a0a8070f7
Closes-bug: #1801873
(cherry picked from commit 1b16725d06)
2019-04-05 09:16:25 -07:00
..
backends LDAP attribute names non-case-sensitive 2018-10-02 14:14:38 +00:00
id_generators Replace six iteration methods with standard ones 2016-09-08 18:56:31 +08:00
mapping_backends Merge "Faster id mapping lookup" 2016-11-01 00:08:36 +00:00
shadow_backends Delete shadow users when domain is deleted 2019-04-05 09:16:25 -07:00
__init__.py Remove exposure of routers at package level 2015-12-03 15:06:56 -03:00
controllers.py Remove log translations in keystone 2017-03-25 18:17:15 +00:00
core.py Delete shadow users when domain is deleted 2019-04-05 09:16:25 -07:00
generator.py Replace keystone.common.config with keystone.conf package 2016-06-24 17:02:15 +00:00
routers.py Implement HEAD method for all v3 GET actions 2016-03-22 10:27:53 -07:00
schema.py Implement better validation for resource options 2017-01-29 13:19:44 -08:00