fusiondirectory-plugins issueshttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues2022-12-07T10:34:10Zhttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/6055Add a basic kerberos plugin2022-12-07T10:34:10ZCôme ChillietAdd a basic kerberos pluginFor now, just show the fields as text fields, so that kerberos information on users is not lost by FD.
https://gitlab.opensides.be/telecomsudparis/Migration-FusionDirectory-OpenLDAP/-/issues/111For now, just show the fields as text fields, so that kerberos information on users is not lost by FD.
https://gitlab.opensides.be/telecomsudparis/Migration-FusionDirectory-OpenLDAP/-/issues/111FusionDirectory 1.5dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/6047A better way of managing SupAnn lists2022-10-25T08:12:49ZbmortierA better way of managing SupAnn lists## Descriptive title for this enhancement
<!-- required -->
designing a better way to manage supann list
### Actual behavior
<!-- What actually happens -->
Actually we read list from disk and those list a created from the bcn
* act...## Descriptive title for this enhancement
<!-- required -->
designing a better way to manage supann list
### Actual behavior
<!-- What actually happens -->
Actually we read list from disk and those list a created from the bcn
* activite_CNU
* activite_REFERENS
* affiliation
* corps_NCORPS
* diplome_SISE
* discipline_SISE
* entite_SUPANN
* etablissement_SUPANN
* eturegimeinscription_SISE
* role_SUPANN
* typediplome_SISE
most of the time the people are not happy with the list because :
* They are huge an not very usefull for their specific cases
* they cannot remove entries in the file because it will be erased on next upgrade
* If the file where not erased but backuped, it still will need manual editing of the file who his cumbersome
### Expected behavior
<!-- What you expect to happen-->
Have to possibility to store lists in the fusiondirectory backend tab supann to replace the lists sroted on disk
### Step by step description of new behaviour
<!-- Required -->
1. Look into his backend to know if a list is filled in the configuration backend
2. If this list is filled it would just use the data from the configuration backend on would not charge the file form disk
we could to that at startup maybe with a flag telling the plugin which list should be taken from disk and wich not
or
we could just flag the list in the configuration backend as used or not used and stored that in seesion so the plugin now where to look for data
### Benefits
<!-- optional -->
<!-- What benefits will be realized by the code change? -->
* Better usability for users
* Better configurability because those list have lots of variations in each location
### Possible Drawbacks
<!-- optional -->
<!-- What are the possible side-effects or negative impacts of the code change? -->
need to think ou to split the supann tab in configuration to not getting huge
### Applicable Issues
full discussion in french https://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/wikis/meeting-supann-list-2020-04-30
<!-- optional -->
<!-- Enter any applicable Issues here -->FusionDirectory 1.5dockx thibaultdockx thibault