Show Advanced KnowledgeHide Advanced Knowledge

Deletion of Inactive Users via Cron (No First Login)

1 Initial Problem

There are two scenarios relevant for this request:

• User accounts are created by an administrator without knowing whether they will ever log in (an dthey actually don't).
• User accounts are created by self-registration but never login afterwards.

Existing cron-jobs for deletion of user accounts require that either they have fallen inactive in some way or the time of their last login has been some time ago.
However, you cannot automatically get rid of user accounts without a first login.

2 Conceptual Summary

A new cron-job is introduced that offers deletion of user accounts without any first login.

3 User Interface Modifications

3.1 List of Affected Views

adm/cron_jobs

3.2 User Interface Details

The cron-job offers the following parameters:

• Schedule (with the same intervals as offered in other cron-jobs)
• Included roles (like with the other deletion cron-jobs)
• Days passed since creation

3.3 New User Interface Concepts

(none)

4 Technical Information

{The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues.}

5 Contact

• Author of the Request: 
• Maintainer: Jansen, Michael [mjansen]
• Implementation of the feature is done by: Jansen, Michael [mjansen]

6 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• Qualitus

7 Discussion

Kunkel, Matthias [mkunkel], 13 AUG 2018 : Why not extending the existing cron-job and cover this use case, too? I do not see a reason to have two separate cron-jobs that tackle inactive users.

Kunkel, Matthias [mkunkel], 13 AUG 2018 : We highly appreciate this suggestion and schedule it for 5.5. Due to different timelines and options, this cron-job should be a distinct cron-job and not merged with one of the existing ones for deactivated users.

8 Implementation

Implemented as described above.

Test Cases

Test cases completed by Qualitus.

• 25074: Ungültige Werte beim Speichern
• 25075: Zeitraum bei Anstoß des Cronjobs noch nicht groß genug
• 25076: Zeitraum bei Anstoß des Cronjobs groß genug
• 25077: Änderung der zu löschenden Rollen
• 25078: Änderung des angegebenen Zeitraums
• 25079: Berücksichtigung keiner Rolle bei Anstoß des Cronjobs
• 25080: Automatischer Crondurchlauf
• 25081: Cronjob wird deaktiviert
• 25082: Benutzer mit Login, ohne Zustimmung der NV
• 25083: Benutzer mit Login, ohne Änderung des PW

Approval

Approved at 2018-12-17 by .