"COPYING" did not exist on "a7dd6a3d28d9b37a2a78a7990b3506f49da9da4c"

Add support for SupAnn CMS (Carte Multi Service)

Documentation: https://services.renater.fr/documentation/supann/supann2018/recommandations2018/personnes/carte-ms

This would add a tab for supannCMS on users, structures and groups (same tab for all three).

I think we should only show to the user the fields supannCMSAffectation and supannCMSAppAffectation as OrderedArrayAttribute attributes.

Other fields would be automatically filled from values of supannCMSAffectation and supannCMSAppAffectation for cards marked as valid (and with an end date in the future).

I guess we’ll need to store IDs in all supported encodings, resulting in a lot of duplicated content.

It will be easier for us to use supannCMSIdEtiquette and supannCMSAppIdDomaine rather than supannCMSId and supannCMSAppId because LDAP attribute options are not easy to deal with in FD. If needed we can still implement something that duplicates the information in the attribute options as well, but most likely it will not be integrated with simpleplugin, and be write-only. (so for instance, these attributes would not have their own ACLs, would not appear in the REST API, and would not be available for hand-written filters in user management)

We’ll need to know possible values for supannCMSType, most likely stored in the config back-end. Same thing for supannCMSSource. Possible domains for supannCMSAppIdDomaine should also appear there.

For technologies and encodings for supannCMSIdEtiquette, we should use nomenclature files like the rest of the supann plugin is doing.

https://gitlab.fusiondirectory.org/telecom-sud-paris/migration-fusiondirectory-openldap/-/issues/69

Edited Aug 17, 2020 by bmortier