nextcloud/lib/private/Authentication
Ferdinand Thiessen 16833aff86
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-09-26 20:48:37 +02:00
..
Events chore: Add SPDX header 2024-05-24 13:11:22 +02:00
Exceptions chore: Add SPDX header 2024-05-24 13:11:22 +02:00
Listeners fix: Make user removal more resilient 2024-09-26 20:48:37 +02:00
Login chore(deps): Update nextcloud/coding-standard to v1.3.1 2024-09-19 14:21:20 +02:00
LoginCredentials chore: Add SPDX header 2024-05-24 13:11:22 +02:00
Notifications feat(notifications): Migrate server INotifiers to new exceptions 2024-06-25 11:56:24 +02:00
Token chore: Add proper deprecation dates where missing 2024-09-20 00:46:03 +02:00
TwoFactorAuth chore: Migrate cleanAppId and getAppPath calls to IAppManager from OC_App 2024-09-13 10:08:43 +02:00
WebAuthn chore(deps): Update nextcloud/coding-standard to v1.3.1 2024-09-19 14:21:20 +02:00