Bug 52202 - Feature Request: Introduce a "Recycle Bin" for user objects
Feature Request: Introduce a "Recycle Bin" for user objects
Status: NEW
Product: UCS
Classification: Unclassified
Component: General
UCS 4.4
Other other
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2020-10-09 17:26 CEST by Michael Grandjean
Modified: 2020-10-12 09:41 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Feature Request
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Grandjean univentionstaff 2020-10-09 17:26:16 CEST
It would be great to have some kind of "Recycle Bin" functionality in UCS.

Scenario: I accidentally delete a user object via UMC or UDM. Instead of actually deleting it, the user object could be a) deactivated and b) moved to a dedicated "Recycle Bin"-tree in the LDAP tree (e.g. OU=recyclebin).
In this case the user could easily be "restored".

Moving a user to the recycle bin could be the default, but there has to be a checkbox/option to bypass the recycle bin, so we can still completely delete a user (just think "DEL" vs. "SHIFT+DEL" on your keyboard).

Variant: In UCS@school the userimport is usually configured to not directly delete users but to deactivate them now and delete them weeks later. Unfortunately, those deactivated users are still visible in all UCS@school modules, take part in the exam mode and are still present and available in external applications. By moving them to a special OU, they would disappear from most of these use cases.

Side effect: unique attributes of the user (username, SID, uidNumber ...) cannot be re-used by a new user as long as the "deleted" user exists in the recycle bin.

Possible obstacles:
- S4- and AD-Connector should probably not just move the user object in Samba/AD, but delete it there because AD has its own concepts for "Deleted objects".
- I thought about having a recycle bin for _all_ LDAP objects and not just for users, but I think there are too many special cases where this wouldn't be a good choice (e.g. objects in cn=temporary).