fusiondirectory issueshttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues2024-03-25T16:25:24Zhttps://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/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/-/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/-/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/-/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/6301[CORE] - Tasks Mail must take into account dynGroups2023-10-31T12:35:03Zdockx thibault[CORE] - Tasks Mail must take into account dynGroupsDyngroup can now be selected thanks to :
https://gitlab.fusiondirectory.org/fusiondirectory/fd/-/merge_requests/1054
In order to get the proper emails of dyngroup members, the task mail must be enhanced.Dyngroup can now be selected thanks to :
https://gitlab.fusiondirectory.org/fusiondirectory/fd/-/merge_requests/1054
In order to get the proper emails of dyngroup members, the task mail must be enhanced.dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6300[CORE] - UsersGroupsRolesAttribute attribute must include dyngroup as well2023-10-31T12:34:24Zdockx thibault[CORE] - UsersGroupsRolesAttribute attribute must include dyngroup as wellFollowing code must be adapted in order to include dyngroup in the below constructor.
['user', 'group', 'role', 'ogroup', 'dyngroup'],
```php
class UsersGroupsRolesAttribute extends ObjectsAttribute
{
function __construct (string $l...Following code must be adapted in order to include dyngroup in the below constructor.
['user', 'group', 'role', 'ogroup', 'dyngroup'],
```php
class UsersGroupsRolesAttribute extends ObjectsAttribute
{
function __construct (string $label, string $description, string $ldapName, bool $required = FALSE, array $defaultValue = [], string $store_attr = 'dn', string $display_attr = 'nameAttr', array $filterElementDefinitions = NULL, string $acl = '')
{
parent::__construct($label, $description, $ldapName, $required, ['user', 'group', 'role', 'ogroup'], $defaultValue, $store_attr, $display_attr, $filterElementDefinitions, $acl);
}
}
```dockx thibaultdockx thibault