New fields are needed to specify the roles defined

[SergioArbarviro]

Additional fields need to be present in the LDAP directory, so that a user can be attributed the roles defined in the specification spreadsheet file.

These fields should not be provided by the user upon registration, but are edted by the LDAP admininstator, according to the situation of the user regarding the corresponding roles.

These additional fields are:

• Member of the Board - boolean - default: false
• Member of the Mediation & Arbitration Council - boolean - default: false
• Member of the Cooperative - boolean - true if and only if the registration process for Cooperators was followed until success
• Content editor - boolean - default: false
• Content translator - boolean - default: false
• Course creator - boolean - default: false
• Course manager - boolean - default: false
• Drupal administrator - boolean - default: false
• Elgg administrator - boolean - default: false
• KuneAgi administrator - boolean - default: false
• LimeSurvey administrator - boolean - default: false
• LiquidFeedback administrator - boolean - default: false
• Mattermost administrator - boolean - default: false
• Moodle administrator - boolean - default: false
• NextCloud / Collabor administrator - boolean - default: false
• Sympa administrator - boolean - default: false

[SergioArbarviro]

The roles specific to some parts of the IT infrastructure are better managed directly by the relevant software. The administrator roles for the elements of the IT infrastructure should be managed directly by the relevant software, to enable a recovery of the site in case of crash of the LDAP or SSO servers. For these two reasons, the only remaining roles to be implemented are:

• Member of the Board,
• Member of the Mediation & Arbitration Council,
• Member of the Cooperative,

which are implemented via #65