Add support for supannConsentement

supannConsentement was added to SupAnn in revision 2.

https://services.renater.fr/documentation/supann/supann2018/recommandations2018/personnes/consentement

• supannConsentement: This is a complicated one, most likely we’ll have to support this as a free field since there is a lot of possible values and tags. It is also hard to exploit when showing data.

This need to be analysed further and be discussed

added plugin-supann label

assigned to @bmortier

mentioned in issue #6024 (closed)

added PJ1802-0188 label

changed due date to January 27, 2020

added 15m of time spent at 2020-01-24

changed the description

mentioned in issue #5906 (closed)

If we want to have something better than a free field for this, we’ll need contrib files to list possible applications and fields. For LDAP fields I’m not sure because there is a whole lot of them so proposing all of them does not sounds good, but showing only the ones active for the user may leak data he’s not supposed to have access to.

So, all in all, maybe we should just leave the admin list in the contrib files allowed ldap fields as well, and for each of them etiquettes if applicable, etc…

added 1h of time spent at 2020-01-29

changed milestone to %FusionDirectory 1.4

changed the description

removed due date

hello @cchilliet,

like discussed in our meeting we should draft the minimal support of supann consentement.

i propose we do it for those attributes at first

• photo
• mail
• contact section attributes in the supan plugin
• cgu

For the implementation i think of having a section in the supann tab of the configuration backend with the value we manage and some value by default.

in the user we have a supann consentement tab that allow to select the value from the configuration and apply the consentement to it

Cheers

mentioned in commit 2aea84b1

added 4h of time spent at 2020-10-01