nextcloud/lib/private/User
Ferdinand Thiessen 7dd85e15b9
fix: Make user removal more resilient
Currently there is a problem if an exception is thrown in `User::delete`,
because at that point the user is already removed from the backend,
but not all data is deleted.

There is no way to recover from this state, as the user is gone no information is available anymore.
This means the data is still available on the server but can not removed by any API anymore.

The solution here is to first set a flag and backup the user home,
this can be used to recover failed user deletions in a way the delete can be re-tried.

Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
2024-10-08 21:02:07 +02:00
..
BackgroundJobs fix: Make user removal more resilient 2024-10-08 21:02:07 +02:00
Listeners chore: Add SPDX header 2024-05-24 13:11:22 +02:00
AvailabilityCoordinator.php Feat: Allow users to select another user as their out-of-office replacement 2024-07-01 15:10:16 +02:00
Backend.php fix: Make user removal more resilient 2024-10-08 21:02:07 +02:00
Database.php feat: Validate password hash 2024-07-08 16:31:42 -07:00
DisplayNameCache.php chore: Add SPDX header 2024-05-24 13:11:22 +02:00
FailedUsersBackend.php fix: Make user removal more resilient 2024-10-08 21:02:07 +02:00
LazyUser.php fix(users): Don't crash if disabled user is missing in the database 2024-09-23 18:06:38 +02:00
LoginException.php chore: Add SPDX header 2024-05-24 13:11:22 +02:00
Manager.php fix(users): Don't crash if disabled user is missing in the database 2024-09-23 18:06:38 +02:00
NoUserException.php chore: Add SPDX header 2024-05-24 13:11:22 +02:00
OutOfOfficeData.php Fix: Make out of office replacement nullable 2024-07-03 12:31:53 +02:00
Session.php fix(Session): avoid race conditions on clustered setups 2024-07-10 13:28:33 +02:00
User.php fix: Make user removal more resilient 2024-10-08 21:02:07 +02:00