Right now IPA allows only to enable/disable users. But disabled users will show up in the searches.
It would make sense to have a more mature user lifecycle management.
Here is an example of what we might want to consider implementing.
When HR team assigns a new account in HR system, the initial user object is stored is provisioned into IPA but it is created in a staging area for example subtree called 'Pending'. Once the account has been created with uid/gid/username calculated, it is
'moved' to ou=Users. When the user terminates, the user object is moved
to say 'Deleted' and is out of the view of normal systems doing user lookups. The object is stored in 'Deleted' until the user returns back (contractor for example). Once the user returns, their object is moved back to the main tree preserving his uid/gid/username/etc attributes.
Group membership should probably not be preserved. However we might want to allow automembership rules trigger on the transfer from Pending to Normal rather than on creation (something to think about).
The account creation/termination process is also SOX-controlled, so we
will need to make sure we have sufficient access control rules and permissions defined regarding who can create, remove or move accounts around.
Looks like a duplicate to #3911...
I have side note: 'User Life Cycle' also includes things like renaming (e.g. after marriage) etc. It would be nice if we can find a solution for such situations.
First part pushed to master:
Part of the previous patch had to be reverted as it stopped generating DNA for objects in cn=trusts,SUFFIX and broke Trusts:
David will help with review.
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1199530
Web UI with prerequisites:
The functionality is there. From now on, the feature is in bugfixing mode.
Metadata Update from @dpal:
- Issue assigned to tbordaz
- Issue set to the milestone: FreeIPA 4.2
to comment on this ticket.