fusiondirectory issueshttps://gitlab.fusiondirectory.org/groups/fusiondirectory/-/issues2024-02-17T00:41:31Zhttps://gitlab.fusiondirectory.org/fusiondirectory/argonaut/-/issues/5782Update the changelog for 1.42024-02-17T00:41:31ZbmortierUpdate the changelog for 1.4Hello,
we need to update the changelog for 1.4
CheersHello,
we need to update the changelog for 1.4
CheersFusionDirectory 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fusiondirectory-orchestrator/-/issues/26[Orchestrator] - Debian packaging issues2024-02-23T18:29:51Zdockx thibault[Orchestrator] - Debian packaging issuesPackaging debian.
Seems like the .htaccess within API is wrongly set, it is folder.
The configuration for apache2 is also within a folder of a folder. /etc/apache2/conf-available/dir/orcherestratorPackaging debian.
Seems like the .htaccess within API is wrongly set, it is folder.
The configuration for apache2 is also within a folder of a folder. /etc/apache2/conf-available/dir/orcherestratordockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6309Support SSHA512 password if overlay pw-sha2 is installed2024-03-28T10:51:25ZJonathan SwaelensSupport SSHA512 password if overlay pw-sha2 is installedHello @tdockx
We need to support SSHA512 password type when pw-sha2 is installed.
FusionDirectory must be able to accept SSHA512 type of password and also to generate them.
CheersHello @tdockx
We need to support SSHA512 password type when pw-sha2 is installed.
FusionDirectory must be able to accept SSHA512 type of password and also to generate them.
CheersFusionDirectory 1.4.1dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fusiondirectory-orchestrator/-/issues/25[Orchestrator] - Enable a logging mechanism to keep any error reported saved2024-02-23T18:34:26Zdockx thibault[Orchestrator] - Enable a logging mechanism to keep any error reported saved[Orchestrator]: Enable a logging mechanism to keep any error reported saved
It would be interesting, as many actions start to be managed by Orchestrator. To keep a log of every action-results in log files.
This can be optional but wou...[Orchestrator]: Enable a logging mechanism to keep any error reported saved
It would be interesting, as many actions start to be managed by Orchestrator. To keep a log of every action-results in log files.
This can be optional but would be a good idea for debugging purposes.
Edit : The human format (jq .) should be used when reading logs.FusionDirectory Orchestrator 1.0dockx 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/6250[Supann] - Configuration backend requires "Account Life Cycle" section2024-01-25T10:17:19Zdockx thibault[Supann] - Configuration backend requires "Account Life Cycle" section1. (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 a...1. (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.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/fusiondirectory-tools/-/issues/49[Tools] Errors reported by Xavier - grpid must be changed2024-02-21T14:43:26Zdockx thibault[Tools] Errors reported by Xavier - grpid must be changed[Tools] Error reported by Xavier
https://gitlab.fusiondirectory.org/fusiondirectory/fusiondirectory-tools/-/merge_requests/37
```bash
/* extract the owner and the group of the directory */
$pwuid = posix_getpwuid($lstat['u...[Tools] Error reported by Xavier
https://gitlab.fusiondirectory.org/fusiondirectory/fusiondirectory-tools/-/merge_requests/37
```bash
/* extract the owner and the group of the directory */
$pwuid = posix_getpwuid($lstat['uid']);
~~ $grgid = posix_getpwuid($lstat['gid']);~~
207 $grgid = posix_getgrgid($lstat['gid']);
~~ printf('Setting %s ower to %s'."\n", $dir, $user);~~
221 printf('Setting %s owner to %s'."\n", $dir, $user);
~~ printf('Setting %s ower to %s'."\n", $dir, $user);~~
257 printf('Setting %s owner to %s'."\n", $dir, $user);
```FusionDirectory Tools 1.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/fusiondirectory-tools/-/issues/48Update CI to add version in tar.gz build-release2024-01-03T09:43:03ZJonathan SwaelensUpdate CI to add version in tar.gz build-releaseUpdate CI to add version in tar.gz build-releaseUpdate CI to add version in tar.gz build-releaseJonathan SwaelensJonathan Swaelenshttps://gitlab.fusiondirectory.org/fusiondirectory/fusiondirectory-orchestrator/-/issues/24[ORCHESTRATOR] - Supann life cycle - automation via Orchestrator2024-02-27T16:25:41Zdockx thibault[ORCHESTRATOR] - Supann life cycle - automation via OrchestratorThe goal of this issue is to develop an automatism being able to manage supannRessourceEtat, the expiry of accounts and their related behavior upon other plugins such as mail. (Partage / Zimbra).
The following steps must be taken into c...The goal of this issue is to develop an automatism being able to manage supannRessourceEtat, the expiry of accounts and their related behavior upon other plugins such as mail. (Partage / Zimbra).
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 - some content is obsolete - see above design document**
1. In the tasks classes of Orchestrator, add a method to retrieve tasks that are set to be redundant and return it. (getTasks() methods without granular filter).
2. Verify the last moment of execution and the schedule date, if scheduleDate < time() then if lastExec is < time() - "redundantOptions" trigger web service call to activate sub-tasks.
- A new class could be developed to manage the web service call towards FusionDirectory. The idea is to be able to click on "executeNow" the daily task in order to have a trace of the execution of that daily task.
- A possible addition to the env file will be required to get all the info related to the web service secure connection
3. In case any sub endpoints of tasks are being triggered, it is wise to first go through the redundant tasks by default and trigger the related tasks.
4. In case of endpoins tasks/supann :
- as said above, trigger redundant tasks, even if not supann.
- only retrieve the subTasks (method getTasks() ) which contains the objectType tasksSupann.
- Any tasks of objectType supann witch are listed, verify the schedule date for that granularTasks (Can be a generic method being used here)
- Verify the “behavior” set in the backend of configuration of FusionDirectory to retrieve what needs to be done.
- Update the DN based on the behavior, see example below. (Account A -> I/S && Mail A -> I/S) etc.
- Create as well a granular task (cn=time()+name of main tasks) related to the main task supannTask to have a trace of what happened. (SupannStatus X changed to Y) with status (2 - completed).
- A documentation on how Orchestrator works to handle this life cycle is required.FusionDirectory Orchestrator 1.0dockx thibaultdockx thibaulthttps://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/user-manual/-/issues/239change the url of rhe depot in 1.3 version of the manual to get the archive f...2023-12-01T10:24:03Zbmortierchange the url of rhe depot in 1.3 version of the manual to get the archive for 1.3.1Hello,
We need to provide access to the archive for people using 1.3.x
CheersHello,
We need to provide access to the archive for people using 1.3.x
Cheersbmortierbmortierhttps://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 thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6305[CORE][Task] - type mail should include a BCC field2024-02-05T16:36:55Zdockx thibault[CORE][Task] - type mail should include a BCC field[CORE][Task]- type mail should include a BCC field
Orchestrator has already the capabilities to integrate BCC but the arrays of attributes returned do not receives replyTo or BCC values yet.[CORE][Task]- type mail should include a BCC field
Orchestrator has already the capabilities to integrate BCC but the arrays of attributes returned do not receives replyTo or BCC values yet.dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/6246Plugin dyngroups missing icons2023-11-26T18:24:21ZFEMAT ORTIZ ArmandoPlugin dyngroups missing icons### Description
We upgrade FusionDirectory 1.4-1 and installed the 'Dyngroup' plugin.
The plugin found the groupsOfUrl. Nevertheless, in the user interface, there are no icons for the Dyngroups.
For information, the [GitLab repository...### Description
We upgrade FusionDirectory 1.4-1 and installed the 'Dyngroup' plugin.
The plugin found the groupsOfUrl. Nevertheless, in the user interface, there are no icons for the Dyngroups.
For information, the [GitLab repository for the plugin](https://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/tree/dev/dyngroups) has no `html` folder. Maybe the problem comes from there.
### Distribution Name and Version
Debian 11 - Bullseye
### FusionDirectory Version
FusionDirectory 1.4-1
### Plugin with the defect
Dyngroup : fusiondirectory-plugin-dyngroups 1.4-1
### PHP version used
PHP : 7.4.33
### Origin of php packages
Distribution package.
### Steps to Reproduce
**Requirements**
- FusionDirectory version 1.4-1 (upgraded from version 1.3-4);
- Dyngroups plugin;
- Having a dynamic group declared.
1. Connecting into FusionDirectory.
2. Entering into the 'Groups and roles' section.
**Expected behavior:**
It is expected to have the icon for Dynamic groups.
**Actual behavior:**
There is no icon nowhere. Some examples:
- The second column of the Groups and roles.
- The Properties column.
- The Actions > Create > Dynamic group.
**Reproduces how often:**
Everytime.FusionDirectory 1.4.1dockx thibaultdockx thibault