Default "System" user

[ywarnier]

In Chamilo 1.11 (and earlier), there is a recurrent issue when a user with privileges (admin being the easiest example) is deleted, as he might have created other users, which then have the "creator_id" set to the deleted user, and inconsistencies arise in some reports after that.
There is also an issue with sending notifications from the portal, as these are usually (initially) associated with the account of the admin who installed the portal.

By creating a "System" account that cannot be deleted and which nobody can "login" into, we could make sure that resources attached to an admin are automatically associated with this "System" account when the admin user is deleted, and we could handle sending notifications in a more neutral way.

Adding this type of user requires an additional field ("can_login") in the user table, and a new user type "system" (maybe type "0" ?) in the list of user types.

This user should also be created automatically during installation and upgrades from 1.11.x.

(BT#19859 is such a case of something going wrong because we lack this mechanism)

[christianbeeznest]

Hi @ywarnier ,

Since DB schema changes aren’t allowed in beta, should we implement the “System” user using logic only (e.g. deny login if username = 'system', prevent deletion by ID), without adding can_login or a new status field?

Let me know if that’s acceptable or if you'd prefer to postpone this.

[ywarnier]

Hi @christianbeeznest
Actually this is much easier now than initially planned: please simply use the "fallback_user" for that. That should solve the issue similarly to what was described above : the fallback_user is already a user without role and a status of 99, planned right for this.

[christianbeeznest]

It's implemented with this PR #6535

Thanks for confirmation.