Cron job for ECS user cleanup

1 Initial Problem

When connecting two (or more) LMS via CampusConnect users will follow course links to the respective other platform. If it is their first time an account will be created for them (ususally via token authentication) which initally has a time limit of only 12 (?) hours. Only when the user joinds a course, this limit is automatically extended to limit set in the ECS configuration (eg. 8 months or whichever value was chose by the admins). Some times users only look around without ever joining a course or group. These accounts then linger in other ILIAS’ database. This creates potential data protection issues as this is unnecessary data retention.

2 Conceptual Summary

A cron job should regularly remove ECS user account that are a) inactive and have b) no course or group memberships.

3 User Interface Modifications

None (?)

3.1 User Interface Details

4 Additional Information

4.1 Involved Authorities

If this request is related to multiple components, please list both authorities for all related components.

4.2 Technical Aspects

{ Necessary technical information have to be provided here, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues. }

4.3 Privacy

{ Personal data that will need to be stored or processed to implement this feature have to be listed here. For each date give a short explanation why it is necessary to use that date. }

4.4 Security

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

4.5 Contact

Person to be contacted in case of questions about the feature or for funding offers:  {Please add related profile link of this person}

4.6 Funding

Funding status and funding parties are listed in the block 'Status of Feature' in the right column of this page.

If you are interested to give funding for this feature, please get into contact with the person mentioned above as 'Contact'.

5 Discussion

6 Implementation

Feature has been implemented by {Please add related profile link of this person}

6.1 Description and Screenshots

{ Description of the final implementation and screenshots if possible. }

6.2 Test Cases

Test cases completed at {date} by {user}

6.3 Privacy

Information in privacy.md of component: updated at {date} by {user} | no change required

6.4 Approval

Approved at {date} by {user}.