Expiring date for users in order to deal with max. number of concurrent users

Organizations with a high number of employees using the "concurrent user license models" hit the limits of UMC when all theoretical employees who should have access get imported as users in order to assign licenses and functional privileges.

This can be mitigated when LDAP or SAML is in scope by enabling the "import at login"-Features. But this will not solve that after a while the environment collected more and more dead user objects.

ARIS currently does not provide a solution for that issue.

A solution could be to introduce a "concurrent user import model": An automated imported user gets marked by an expiration date after which the corresponding user object gets deleted from UMC automatically. Or a deletion getting performed after a period of inactivity.

Once the deleted user returns to ARIS the auto-import-features will re-import the user object from LDAP or SSO and the end-user will not experience any disadvantages.

This would not only solve the corresponding performance and resource impacts, but it would enable ARIS also to deal in the future with much higher potential amounts of users.