Browse Source

Delete SQL users before deleting domain

Since the users table has a foreign key to the projects table[1], users
must be deleted before the domain can be deleted. However, the
notification emitted from the domain deletion comes too late, and
keystone runs into a foreign key reference error before it can delete
the users. This patch addresses the problem by adding a new internal
notification to alert the identity manager that users should be deleted.
This uses a new notification rather than the existing notification
because the existing one is used to alert listeners that the domain
deletion has been fully completed, whereas this one must happen in the
middle of the domain delete process.

The callback must also only try to delete SQL users. The LDAP driver
doesn't support deleting users, and we can't assume other drivers
support it either. Moreover, the foreign key reference is only a problem
for SQL users anyway.

Because our backend unit tests run with SQLite and foreign keys do not
work properly, we can't properly expose this bug in our unit tests, but
there is an accompanying tempest test[2][3] to validate this fix.


Change-Id: If5bdb6f5eef80b50b000aed5188ce7da4dfd1083
Closes-bug: #1718747
Colleen Murphy 2 years ago
4 changed files with 35 additions and 2 deletions
  1. +14
  2. +1
  3. +3
  4. +17

+ 14
- 2
keystone/identity/ View File

@@ -486,10 +486,12 @@ class Manager(manager.Manager):
def __init__(self):
super(Manager, self).__init__(CONF.identity.driver)
self.domain_configs = DomainConfigs()

notifications.ACTIONS.internal, notifications.DOMAIN_DELETED,
self.event_callbacks = {
notifications.ACTIONS.deleted: {
'domain': [self._domain_deleted],
'project': [self._unset_default_project],
@@ -498,6 +500,16 @@ class Manager(manager.Manager):
domain_id = payload['resource_info']

driver = self._select_identity_driver(domain_id)

if not driver.is_sql:
# The LDAP driver does not support deleting users or groups.
# Moreover, we shouldn't destroy users and groups in an unknown
# driver. The only time when we should delete users and groups is
# when the backend is SQL because the foreign key in the SQL table
# forces us to.

user_refs = self.list_users(domain_scope=domain_id)
group_refs = self.list_groups(domain_scope=domain_id)

+ 1
- 0
keystone/ View File

@@ -80,6 +80,7 @@ INVALIDATE_USER_TOKEN_PERSISTENCE = 'invalidate_user_tokens'
INVALIDATE_USER_PROJECT_TOKEN_PERSISTENCE = 'invalidate_user_project_tokens'
INVALIDATE_USER_OAUTH_CONSUMER_TOKENS = 'invalidate_user_consumer_tokens'
INVALIDATE_TOKEN_CACHE_DELETED_IDP = 'invalidate_token_cache_from_deleted_idp'
DOMAIN_DELETED = 'domain_deleted'

class Audit(object):

+ 3
- 0
keystone/resource/ View File

@@ -773,6 +773,9 @@ class Manager(manager.Manager):

notifications.DOMAIN_DELETED, domain_id
self._delete_project(domain_id, initiator)
self.get_domain.invalidate(self, domain_id)

+ 17
- 0
releasenotes/notes/bug-1718747-50d39fa87bdbb12b.yaml View File

@@ -0,0 +1,17 @@
- |
[`bug 1718747 <>`_]
Fixes a regression where deleting a domain with users in it caues a server
error. This bugfix restores the previous behavior of deleting the users
namespaced in the domain. This only applies when using the SQL identity
- |
[`bug 1718747 <>`_]
As part of solving a regression in the identity SQL backend that prevented
domains containing users from being deleted, a notification callback was
altered so that users would only be deleted if the identity backend is SQL.
If you have a custom identity backend that is not read-only, deleting a
domain in keystone will not delete the users in your backend unless your
driver has an is_sql property that evaluates to true.