Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
fusiondirectory-plugins
fusiondirectory-plugins
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 47
    • Issues 47
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • fusiondirectory
  • fusiondirectory-pluginsfusiondirectory-plugins
  • Issues
  • #6015

Closed
Open
Opened Nov 26, 2019 by Côme Chilliet@cchillietDeveloper

Add support for SupAnn CMS (Carte Multi Service)

Related to #5906

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
Assignee
Assign to
FusionDirectory 1.4
Milestone
FusionDirectory 1.4
Assign milestone
Time tracking
None
Due date
None
Reference: fusiondirectory/fd-plugins#6015