fusiondirectory issueshttps://gitlab.fusiondirectory.org/groups/fusiondirectory/-/issues2024-03-29T00:41:29Zhttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6321[Tasks] - Make the generic tasks even more generic, allowing the object type ...2024-03-29T00:41:29Zdockx thibault[Tasks] - Make the generic tasks even more generic, allowing the object type string to be custom in case of added plugins[Tasks] - Make the generic tasks even more generic, allowing the object type string to be custom in case of added plugins
Currently, the creation of subTasks is handled by :
`public function createSlaveTasks (array $listOfDN, string $a...[Tasks] - Make the generic tasks even more generic, allowing the object type string to be custom in case of added plugins
Currently, the creation of subTasks is handled by :
`public function createSlaveTasks (array $listOfDN, string $attributeType, array $attrs = NULL): void`
example :
```php
// Call the method from parent tasks object (first tab) to create sub-tasks.
$this->parent->getBaseObject()->createSlaveTasks($listOfDN, $attributeType);
```
The variable attributeType was previously set for life cycle and mail tasks. (fdTasksGranularDN, fdTasksGranularMail).
To differentiate the usage of DN (CN/UID or MAIL).
We can still use that logic that could become beneficial for harder tasks in the future, set in the CORE.
_Currently, a new argument should be passed to define fdTasksGranularType._
Modification should occur here :
```php
case 'fdTasksGranularDN' :
$prepData['tasksGranular'] = [
"fdTasksGranularDN" => $dn,
"fdTasksGranularType" => 'Life Cycle',
];
break;
}
```
Life Cycle was hard-coded on purpose but could definitely receive a string variable now.
As more plugins will be developed, such as notifications, which also base itself on the concept of "pure" DN such as life cycle.
**Added Note**
LastExec is currently using date format based on time() which is unix UTC format.
Somehow using Date changes the local dateTime to local time. We have to have UTC globally.
gmDate instead of Date could resolve the issue easily. As generalizeTime in FD use Z which is UTC already.FusionDirectory 1.5dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6320[Tasks] - Mail class can have one method static to be reused outside object c...2024-03-25T16:25:24Zdockx thibault[Tasks] - Mail class can have one method static to be reused outside object call by others[Tasks] - Mail class can have one method static to be reused outside object call by others
```
// send the objectype and attrs name to the below method
$this->setEmailsFromSelectedDN($mailObject, $mailAttr);
```
The above metho...[Tasks] - Mail class can have one method static to be reused outside object call by others
```
// send the objectype and attrs name to the below method
$this->setEmailsFromSelectedDN($mailObject, $mailAttr);
```
The above method can be statically called and shared outside group instance.FusionDirectory 1.5dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/dev-manual/-/issues/85[Dev-Manual] - Update of the new plugin schema ID2024-03-25T10:20:24Zdockx thibault[Dev-Manual] - Update of the new plugin schema ID[Dev-Manual] - Update of the new plugin schema ID for Notifications.
Current last being use is : dolibarr-fd.schema - 89
Notifications will use 90 for is default schema and 91 for its configuration[Dev-Manual] - Update of the new plugin schema ID for Notifications.
Current last being use is : dolibarr-fd.schema - 89
Notifications will use 90 for is default schema and 91 for its configurationFusionDirectory 1.5dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fusiondirectory-orchestrator/-/issues/40[Orchestrator] - Re-activate failed sub-tasks linked to a specific main task.2024-03-25T11:06:14Zdockx thibault[Orchestrator] - Re-activate failed sub-tasks linked to a specific main task.[Orchestrator] - Re-activate failed sub-tasks linked to a specific main task.
The concept is to be able to re-activate failed tasks via the specification of the "main" task related.[Orchestrator] - Re-activate failed sub-tasks linked to a specific main task.
The concept is to be able to re-activate failed tasks via the specification of the "main" task related.FusionDirectory 1.5dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/6258[NewPlugin] - Notifications, based on automatic snapshots, send email to requ...2024-03-28T11:09:02Zdockx thibault[NewPlugin] - Notifications, based on automatic snapshots, send email to required personal about attributes changes[NewPlugin] - Notifications, based on automatic snapshots, send email to required personal about attributes changes.
A design document can be found in the gitlab documentation [Here](https://gitlab.fusiondirectory.org/documentation/fusi...[NewPlugin] - Notifications, based on automatic snapshots, send email to required personal about attributes changes.
A design document can be found in the gitlab documentation [Here](https://gitlab.fusiondirectory.org/documentation/fusiondirectory-fusiondirectory/-/tree/master/designs-documents)
Le concept est d'envoyer un e-mail à un individu, un responsable, un gestionnaire, en fonction de la modification d'un ou plusieurs attribut(s) spécifique(s).
L'idée générale est d'utiliser le mécanisme des instantanés automatiques, une nouvelle tâche de type "Notifications" et la configuration du backend grâce à un nouveau plugin "Notifications" permettant de définir des attributs spécifiques qui doivent être vérifiés s'ils ont été modifiés.
La nouvelle tâche de notification sera une tâche cyclique, réglée par défaut sur une fréquence horaire. Une fois la tâche activée, elle collectera les DN des utilisateurs en se basant sur l'horodatage des snapshots pris pour ces utilisateurs et la dernière exécution de la tâche. Création de sous-tâches pertinentes, comme d'habitude, de type Notifications.
Ces nouvelles tâches pourront sélectionner une liste d'attributs définis précédemment dans la configuration du backend et une liste d'utilisateurs où la notification doit être envoyée.
Plusieurs changements sont nécessaires pour l'Orchestrator :
- Orchestrator fonctionnera donc comme d'habitude sur la base de sa configuration cron, en activant des tâches cycliques si cela est nécessaire.
- Un nouveau point de terminaison "notifications" sera créé, permettant de passer en revue toutes les sous-tâches de notification.
Dans la sous-tâche se trouvera le DN de l'utilisateur où les instantanés ont été pris, il y aura une vérification basée sur les attributs des tâches principales énumérés, si un attribut a changé, il doit être notifié. Une liste doit être produite
- Si une notification est nécessaire, envoyez un courriel au responsable éventuel de cet utilisateur spécifique et signalez l'état des sous-tâches. Si aucune modification n'est nécessaire, les sous-tâches concernées seront supprimées.
Ce ticket supportera les changements sous format plugin de :
- Schema LDAP notifications.schema et notifications-conf.schema
- Un nouveau tab pour "Tasks" permettant la configuration de notifications (membres et attributs)
- Un nouveau tab dans configuration (backend) permettant la configuration des attributs devant / pouvant etre suivis par la tache.FusionDirectory 1.5dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6316[CORE] - Snapshots - listing view of modifications per snapshot2024-03-12T16:18:45Zdockx thibault[CORE] - Snapshots - listing view of modifications per snapshot[CORE] - Snapshots - listing view of modifications per snapshot
Within the restoration management page of snapshots, it would be great to be able to visual easily the LDIF of a selected snapshot.
It would be great to also have the possi...[CORE] - Snapshots - listing view of modifications per snapshot
Within the restoration management page of snapshots, it would be great to be able to visual easily the LDIF of a selected snapshot.
It would be great to also have the possibility to export the snapshots' history, explain which data has been modified and a which date.
Without forgetting the current data present on the user file.
Without forgetting to set a better text message saying that automatic snapshots is only present for user (for now).FusionDirectory 1.5dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/6256delete server systems delete user manager2024-03-25T09:16:25Zemmanuel thetasdelete server systems delete user manager### Description
delete system server, workstation etc delete user manager
### Distribution Name and Version
debian 11
### FusionDirectory Version
1.4
### PHP version used
7.4
### Origin of php packages
Distribution packages
##...### Description
delete system server, workstation etc delete user manager
### Distribution Name and Version
debian 11
### FusionDirectory Version
1.4
### PHP version used
7.4
### Origin of php packages
Distribution packages
### Steps to Reproduce
1. Install fusiondirectory 1.4 with systems plugins, empty ldap
2. create 2 users, do user1 like manager on user2
3. create a server (for example) in systems
4. delete this server
5. manager on user2 is empty
**Expected behavior:**
no change on user data
**Actual behavior:**
deletion of manager attribut
**Reproduces how often:**
100%
### Additional InformationFusionDirectory 1.5dockx thibaultdockx thibaulthttps://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/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/fd-plugins/-/issues/6257system template error2024-03-12T16:26:25Zemmanuel thetassystem template error### Description
when validate a new system template,
### Distribution Name and Version
debian 11
### FusionDirectory Version
1.4
### PHP version used
PHP 7.4.33
### Origin of php packages
Distribution packages
### Steps to Re...### Description
when validate a new system template,
### Distribution Name and Version
debian 11
### FusionDirectory Version
1.4
### PHP version used
PHP 7.4.33
### Origin of php packages
Distribution packages
### Steps to Reproduce
1. add systems template
2. add dhcp tab
3. validate!
4. [template](/uploads/41f83423bd28c53d8c62b9169595fe80/template.png)
**Expected behavior:**
save template
**Actual behavior:**
when add template with dhcp tab:
Erreur Fatale
Non attrapé : TypeError : Argument 4 passed to DhcpHostsAttribute::postLdapSave() must be of the type array, string given, called in /usr/share/fusiondirectory/plugins/admin/systems/class_dhcpSystem.inc on line 412
when delete template :
Non attrapé : TypeError : Argument 2 passed to dnsHost::removeIpsFromZones() must be of the type array, string given, called in /usr/share/fusiondirectory/plugins/admin/systems/class_dnsHost.inc on line 504
**Reproduces how often:**
100%
### Additional Information
template save anywayFusionDirectory 1.5dockx thibaultdockx thibaulthttps://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/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/-/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/-/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/6303[CORE][MAIL] – Attachments for emails must be created as sub nodes2024-01-22T09:53:32Zdockx thibault[CORE][MAIL] – Attachments for emails must be created as sub nodes[CORE][MAIL] – Attachments for emails must be created as sub nodes
The idea is like FAI script, able to adds multiple entry within an array.
Sub nodes will be created under the parent CN.
This allows taking all enclosed files and ...[CORE][MAIL] – Attachments for emails must be created as sub nodes
The idea is like FAI script, able to adds multiple entry within an array.
Sub nodes will be created under the parent CN.
This allows taking all enclosed files and their related names correctly.FusionDirectory 1.5dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6302[CORE][TASKS] - Tasks must be set as repeatable and updatable2023-10-31T12:33:48Zdockx thibault[CORE][TASKS] - Tasks must be set as repeatable and updatable[CORE][TASKS] – Tasks must be set as repeatable and updatable
The concept is the following :
- **Repeatable**
- Makes a task able to repeat based on the time (days / Hours) set in the task settings.
- By default, re-create subtasks...[CORE][TASKS] – Tasks must be set as repeatable and updatable
The concept is the following :
- **Repeatable**
- Makes a task able to repeat based on the time (days / Hours) set in the task settings.
- By default, re-create subtasks for ALREADY existing members. (If updatable field not set).
- **Updatable**
- Allows creation of sub-tasks ONLY for new members (Context of dynamic group).FusionDirectory 1.5dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6297[CAS] - Issues with discovered SLO (SSO) not implemented. Making a new SSO au...2024-03-05T18:03:13Zdockx thibault[CAS] - Issues with discovered SLO (SSO) not implemented. Making a new SSO auth validated not used and last login (session) being used.[CAS] – Issues with discovered SLO (SSO) not implemented. Making a new SSO auth validated not used and last login (session) being used.
Please follow the below link to some information.
- https://apereo.github.io/cas/6.5.x/installatio...[CAS] – Issues with discovered SLO (SSO) not implemented. Making a new SSO auth validated not used and last login (session) being used.
Please follow the below link to some information.
- https://apereo.github.io/cas/6.5.x/installation/Logout-Single-Signout.html
- https://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6088
The current CAS (v1.6 not verified) - does not properly logout / remove (adapt) user sessions.FusionDirectory 1.5dockx thibaultdockx thibault