fusiondirectory issueshttps://gitlab.fusiondirectory.org/groups/fusiondirectory/-/issues2024-03-12T16:17:01Zhttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6314[CORE] - Snapshots - review of the current automatic creation logic2024-03-12T16:17:01Zdockx thibault[CORE] - Snapshots - review of the current automatic creation logic[CORE] - Snapshots - review of the current automatic creation logic
There are currently multiple issues :
- The first automatic snapshot only contains data from tab USER
- Other tabs are not considered when USER is not updated
- When ta...[CORE] - Snapshots - review of the current automatic creation logic
There are currently multiple issues :
- The first automatic snapshot only contains data from tab USER
- Other tabs are not considered when USER is not updated
- When tab USER is updated, only the last values of other tabs are being saved.
**Team Discussion**
__CONSTRUCT must have the automatic creation and related verification within.
- If no modification, verification based on the MD5 stored in previous snapshots (new attribute schema).
Only the first tab __construct should contain the snapshot creation call
- IF automatic snapshots is allowed.
- IF MD5 verification is not equal.
The concept is based on the creation of the existing into snapshots, not the modification.
In the project of notifications via Orchestrator - there will be a verification upon the last snapshots and the existing user information.FusionDirectory 1.5dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/user-manual/-/issues/245freeradius url error2024-03-12T08:04:38Zemmanuel thetasfreeradius url errorin page :
https://fusiondirectory-user-manual.readthedocs.io/en/1.4/fusiondirectory/plugins/freeradius/installation.html
wrong url for "freeradius official schema" in Install schemas
https://github.com/FreeRADIUS/freeradius-server/blo...in page :
https://fusiondirectory-user-manual.readthedocs.io/en/1.4/fusiondirectory/plugins/freeradius/installation.html
wrong url for "freeradius official schema" in Install schemas
https://github.com/FreeRADIUS/freeradius-server/blob/master/doc/schemas/ldap/openldap/freeradius.schema
is a 404 page
i think it s
https://github.com/FreeRADIUS/freeradius-server/blob/master/doc/schemas/ldap/openldap/freeradius-radius.schemaFusionDirectory 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/6255[Samba] - Samba tab cannot be removed when samba ID mapping is activated2024-03-07T11:23:13Zdockx thibault[Samba] - Samba tab cannot be removed when samba ID mapping is activated[Samba] - Samba tab cannot be removed when samba ID mapping is activated[Samba] - Samba tab cannot be removed when samba ID mapping is activatedFusionDirectory 1.5dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6312[Tasks] - Allow an array of members emails for BCC - Mail Template2024-03-05T14:44:45Zdockx thibault[Tasks] - Allow an array of members emails for BCC - Mail Template[Tasks] - Allow an array of members emails for BCC, as one string (one email) is not sufficient for most clients[Tasks] - Allow an array of members emails for BCC, as one string (one email) is not sufficient for most clientsFusionDirectory 1.5dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/user-manual/-/issues/244Change the core/main menu into the documentation to reflect the new FusionDir...2024-02-24T11:06:18ZbmortierChange the core/main menu into the documentation to reflect the new FusionDirectory menu organisationHello,
We reorganized the main menu in FusionDirectory, but this is not reflected into the documentation
CheersHello,
We reorganized the main menu in FusionDirectory, but this is not reflected into the documentation
CheersFusionDirectory 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6310Add a screenshot dirrectory into the contrib directory to be used by the yaml...2024-02-24T10:46:53ZbmortierAdd a screenshot dirrectory into the contrib directory to be used by the yaml and the marketplaceHello,
We need a screenshot directory into the contrib directory to place the screenshot that will be used in the yaml for the marketplace
CheersHello,
We need a screenshot directory into the contrib directory to place the screenshot that will be used in the yaml for the marketplace
CheersFusionDirectory 1.5bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/6254Add a screenshot dirrectory into the contrib directory to be used by the yaml...2024-02-24T10:46:37ZbmortierAdd a screenshot dirrectory into the contrib directory to be used by the yaml and the marketplaceHello,
We need a screenshot directory into the contrib directory to place the screenshot that will be used in the yaml for the marketplace
CheersHello,
We need a screenshot directory into the contrib directory to place the screenshot that will be used in the yaml for the marketplace
CheersFusionDirectory 1.5bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fusiondirectory-orchestrator/-/issues/33Update the readme.md2024-02-23T20:06:13ZbmortierUpdate the readme.mdHello,
We need to update the readme.md with the inftomation for the user manual to tell what is FusionDirectory Orchestrator
CheersHello,
We need to update the readme.md with the inftomation for the user manual to tell what is FusionDirectory Orchestrator
CheersFusionDirectory Orchestrator 1.0bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/user-manual/-/issues/242change the wording for the professional support and urls2024-02-24T10:49:20Zbmortierchange the wording for the professional support and urlsHello,
we need to change the wording because we have subscription now and not only support
CheersHello,
we need to change the wording because we have subscription now and not only support
CheersFusionDirectory 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/6253[WebService] - Tokens system to be put in place instead of password usage2024-02-20T15:16:23Zdockx thibault[WebService] - Tokens system to be put in place instead of password usage**The general concept**
The idea is to set in place a new tab on the User, allowing the generation of a token with a specific end date.
The concept is not to use the password to interact with the web service but a defined token.
...**The general concept**
The idea is to set in place a new tab on the User, allowing the generation of a token with a specific end date.
The concept is not to use the password to interact with the web service but a defined token.
We would keep the specific ACL verification currently in place, but the idea is to use a time-driven web service access.
More or less the same behavior as GitLab.
There was an idea to use a "DSA" to interact with FD web service, but DSA is strictly used for LDAP interaction and should not be used with the web service.
**Possible developments**
- Maybe CORE login methodology to add verification of tokens instead of passwords when interacting with web service.
- Web service schema
- New tab on User.
- Logic to be re-defined within web service classes to manage authentication access.
- The token would therefore be the only one used to authenticate.
- Password is to be removed from the allowed authentication logic.FusionDirectory 1.5dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/6252[NewPlugin] - Location - Lieu - Allowing specific attributes related to user ...2024-02-19T22:01:36Zdockx thibault[NewPlugin] - Location - Lieu - Allowing specific attributes related to user location to be defined within a new TAB**The general concept**
The idea is a new tab available in the backend of configuration allowing the admins to define :
- Sites
- Building
- Floor
- Desk
Or other required location settings, such as defining (?boolean) usage of supan...**The general concept**
The idea is a new tab available in the backend of configuration allowing the admins to define :
- Sites
- Building
- Floor
- Desk
Or other required location settings, such as defining (?boolean) usage of supann structures.
**Two usages**
_With supann_
The idea is to have the supann structures to have the information about the location, such as site, floor, desks…
This information can be referenced on Entity as well as on Establishment.
Users (File of individual) - can be linked, if using supann, to multiple entities / establishment.
A new tab, location - lieu, will be available with a reduced list of choices based on which entities and / or establishments he is linked with.
_Without supann_
The idea is to have the new tab present on the User (File of individual) with all possible options defined within the backend configuration.
The new plugin would therefore allow usage of the full concept with or without supann attached.dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6308Having a way to create ordered away with a column as reference2024-02-06T14:34:00ZJonathan SwaelensHaving a way to create ordered away with a column as referenceHello @tdockx
When we add elements, it would be nice to have a way to specify which column must be seen as reference in so that we cannot have multiple entries.
It would be nice to have a concept of one unique key instead of one key w...Hello @tdockx
When we add elements, it would be nice to have a way to specify which column must be seen as reference in so that we cannot have multiple entries.
It would be nice to have a concept of one unique key instead of one key with multiple status. With the latest one overwritting the old one).dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/6251[MAIL] - Modify the direct trigger of sync capabilities for Zimbra and Partage2024-01-25T10:24:37Zdockx thibault[MAIL] - Modify the direct trigger of sync capabilities for Zimbra and Partage~~(Plugins) An update of the plugin tab Mail containing calls to Partage and Zimbra is required, if tick box of "usage of Orchestrator" is set within Supann backend configuration, the plugin should not perform anything itself.~~
It has ...~~(Plugins) An update of the plugin tab Mail containing calls to Partage and Zimbra is required, if tick box of "usage of Orchestrator" is set within Supann backend configuration, the plugin should not perform anything itself.~~
It has been decided to create conditions within Renater and Zimbra plugins to handle this individually.
This allows more flexibility in the case of multiple servers being registered with different behavior required.dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/6249Import eduPerson schema for orcid2024-03-19T09:43:35Zdockx thibaultImport eduPerson schema for orcidIt would be very usefull to import/merge the eduPerson 2021-11 schema in fd to support orcid. Currently FD use it own schema and attribute to store the orcid.
Because other applications expect to use the correct (= official) [attribute]...It would be very usefull to import/merge the eduPerson 2021-11 schema in fd to support orcid. Currently FD use it own schema and attribute to store the orcid.
Because other applications expect to use the correct (= official) [attribute](https://wiki.refeds.org/display/STAN/eduPerson+2021-11#eduPerson202111-eduPersonOrcidl) it is a little useless to enter the orcid information in a custom attribute known only by FD.FusionDirectory 1.4.1dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/user-manual/-/issues/241add the new configuration for the fusiondirectory configuration partage backe...2024-02-22T09:23:26Zbmortieradd the new configuration for the fusiondirectory configuration partage backend configurationHello,
we need to add to the manual, the new configuration for partage that has been added in 1.4 following renater partage development
CheersHello,
we need to add to the manual, the new configuration for partage that has been added in 1.4 following renater partage development
CheersFusionDirectory 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/user-manual/-/issues/240[Orchestatrator] - user manual installation - prerequis2024-03-22T15:32:22Zdockx thibault[Orchestatrator] - user manual installation - prerequisNous avons besoin de préciser qu'il s'agit de PHP 7.4 en obligatoire et non pas 7.3 pour orchestrator
Ainsi pour les utilisateurs centos : yum-config-manager --enable remi-php73 doit être mis en 74 pour orchestrator. (Note, cela n'est i...Nous avons besoin de préciser qu'il s'agit de PHP 7.4 en obligatoire et non pas 7.3 pour orchestrator
Ainsi pour les utilisateurs centos : yum-config-manager --enable remi-php73 doit être mis en 74 pour orchestrator. (Note, cela n'est indiqué nul part pour orchestrator, uniquement pour FD. : https://gitlab.fusiondirectory.org/fusiondirectory/user-manual/-/blob/1.4/source/fusiondirectory-orchestrator/install/debian/debian-orchestrator-install.rst à mettre ici sans doute avec repo remi centos)
https://gitlab.fusiondirectory.org/fusiondirectory/user-manual/-/blob/1.4/source/fusiondirectory-orchestrator/prerequisite/prerequisite.rstFusionDirectory Orchestrator 1.0bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6307[CORE] - Supann life cycle - automation via Orchestrator2024-03-05T18:04:31Zdockx thibault[CORE] - Supann life cycle - automation via OrchestratorThe goal is to have FusionDirectory tasks system, embedded within its core, ready for Orchestrator when the automatism of supann life cycle is being developed.
The following steps must be taken into consideration. **(OBSOLETE)**
Please ...The goal is to have FusionDirectory tasks system, embedded within its core, ready for Orchestrator when the automatism of supann life cycle is being developed.
The following steps must be taken into consideration. **(OBSOLETE)**
Please confer to the simple design document that can be found here : [Cycle_de_vie_-_development_-_design_document__DRAFT__.odt](/uploads/f967363d809fb7f8d2ba1c7b7d0266b4/Cycle_de_vie_-_development_-_design_document__DRAFT__.odt)
**Note that this document is subject to update and is definitely not in its final form**
**BELOW contains historical design - somecontent is obsolete - see above design document**
1. A new attribute in tasks generic must best added, and the schema therefore must be modified to have the "lastExec" date present. (Done).
2. The generic task must be updated accordingly if tab supann is selected:
- The redundancy should be automatically set to daily, and the case “new members only” should be unpicked. (Done).
- The mail tab should therefore not be possible to be activated. (Done)
- A message when opening the tab supann should appear explaining this behavior. (It makes no sense to no do it as supannRessourceEtat are fix dates - daily check). (Done)
3. The tab supann Task
- ObjectClass supannTask, should make visible the behavior set in the configuration backend. Read-only. With message to change it in the configuration if required. (No schema update as noLdapSave).
- The list of members will be processed automatically, only the members having an active account with expired date as end.
- The creation of subtasks will be triggered the same way as for the mail tasks, only, maybe lesser information required. Although emails in subclass can be left as is. Still is a referenced to the user account.
4. (Plugins) FD must have an updated schema of supann-fd-conf as we need to add a new section about the behavior required in case of Account closure.
- This must include a tick box saying that we will manage this via Orchestrator
- An array of related existing supannRessourceEtat should be available and a matching with the behavior required for others supannRessourceEtat.
- An array of one-to-one match departing from AccountStatus seems the good way to perform it.
5. (Plugins) An update of the plugin tab Mail containing calls to Partage and Zimbra is required, if the above tick box of "usage of Orchestrator" is set, the plugin should not perform anything itself.
6. A documentation on all this process is required in sphinx on FD core website.FusionDirectory 1.5dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/6248Update or add a method to be able to apply a template to existant user by the...2023-12-06T16:26:21ZJonathan SwaelensUpdate or add a method to be able to apply a template to existant user by the webserviceHello @tdockx
Right now, we can only use the template when we create new users through the web service, it would be wonderful to be able to apply it to an existent user so that we get the same comportment of the interface.
I think tha...Hello @tdockx
Right now, we can only use the template when we create new users through the web service, it would be wonderful to be able to apply it to an existent user so that we get the same comportment of the interface.
I think that the following links are related
- https://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/blob/dev/webservice/include/webservice/class_fdRPCService.inc#L688
- https://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/blob/dev/webservice/html/rest.php#L362FusionDirectory 1.5dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/6247[Invitations] - Problems with location of public form and template resulting ...2023-12-04T09:57:41Zdockx thibault[Invitations] - Problems with location of public form and template resulting in wrong baseWhen a public form with a non-root creation base is used by an invitation that isn't stored on root, the two bases are combined resulting in an (usually) invalid root, causing the form to error. If base is left as an altered field in the...When a public form with a non-root creation base is used by an invitation that isn't stored on root, the two bases are combined resulting in an (usually) invalid root, causing the form to error. If base is left as an altered field in the public form, it is either similarly not handled correctly, or is ignored entirely, I was not able to verify which in my troubleshooting. It does seem that if you leave the invitation at root, but set a non-root value for the creation base for the public form, it will initially create the user and their registration at the creation base defined in the public form, but then move it to root when you confirm the user.
To Reproduce
Create a public form with a creation base other than root
Create an invitation that uses that public form and store it somewhere other than root
Send that invitation to yourself and fill in the form
Assuming the resultant mess of combined base doesn't exist in your directory, the form will fail
https://github.com/fusiondirectory/fusiondirectory-plugins/issues/36dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6306[CORE] - Issues of services not triggered by account deactivation via lock ic...2023-12-21T09:24:42Zdockx thibault[CORE] - Issues of services not triggered by account deactivation via lock icon on user list[CORE] - Issues of services not triggered by account deactivation via lock icon on user list[CORE] - Issues of services not triggered by account deactivation via lock icon on user listFusionDirectory 1.5dockx thibaultdockx thibault