fusiondirectory issueshttps://gitlab.fusiondirectory.org/groups/fusiondirectory/-/issues2024-03-28T10:51:25Zhttps://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/41[Orchestrator] MAIL_SEC="<ssl/tls"> error typo in the orchestrator configuration2024-03-26T11:49:11Zdockx thibault[Orchestrator] MAIL_SEC="<ssl/tls"> error typo in the orchestrator configuration[Orchestrator] MAIL_SEC="<ssl/tls"> error typo in the orchestrator configuration.
" should be fixed to not throw error in case mail is left untouched.[Orchestrator] MAIL_SEC="<ssl/tls"> error typo in the orchestrator configuration.
" should be fixed to not throw error in case mail is left untouched.FusionDirectory 1.5dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/user-manual/-/issues/215change the install method for fusondirectory 1.42024-03-14T20:24:03Zbmortierchange the install method for fusondirectory 1.4Hello,
in FusionDirectory 1.4 we have new repositories and a more logical approach due to the number of distribution we support
we decided for the following architecture
- fusiondirectory
- fusiondirectory-integrator
- fusiondirectory...Hello,
in FusionDirectory 1.4 we have new repositories and a more logical approach due to the number of distribution we support
we decided for the following architecture
- fusiondirectory
- fusiondirectory-integrator
- fusiondirectory-orchestrator
- fusiondirectory-utilities
- fusiondirectory-external-libraries
fusiondirectory-utilities and fusiondirectory-external-libraries are meta repos of our tools and needed external libraries
All the repositories are arranged with the name of the distribution to serve a a separator
All the libraries are on build on bullseye only because they don't change between distributions
ex:
#### buster
```
#fusiondirectory repository
deb https://public.fusiondirectory.org/debian/buster-fusiondirectory-release/ buster main
#fusiondirectory integrator
deb https://public.fusiondirectory.org/debian/fusiondirectory-integrator/ bulleyes main
#fusiondirectory utilities
deb https://public.fusiondirectory.org/debian/fusiondirectory-utilities/ bulleyes main
#fusiondirectory libraries
deb https://public.fusiondirectory.org/debian/fusiondirectory-external-libraries/ bullseye main
```
#### Bullseyes
```
#fusiondirectory repository
deb https://public.fusiondirectory.org/debian/buster-fusiondirectory-release/ bullseye main
#fusiondirectory integrator
deb https://public.fusiondirectory.org/debian/fusiondirectory-integrator/ bulleyes main
#fusiondirectory utilities
deb https://public.fusiondirectory.org/debian/fusiondirectory-utilities/ bulleyes main
#fusiondirectory libraries
deb https://public.fusiondirectory.org/debian/fusiondirectory-external-libraries/ bullseye main
```
CheersFusionDirectory 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fusiondirectory-tools/-/issues/58[Tools] - import the new fusiondirectory-orchestrator-client within tools2024-03-14T13:04:03Zdockx thibault[Tools] - import the new fusiondirectory-orchestrator-client within tools[Tools] - import the new fusiondirectory-orchestrator-client within tools[Tools] - import the new fusiondirectory-orchestrator-client within toolsdockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fusiondirectory-orchestrator/-/issues/36[Orchestrator] - Adapt CI to integrate new FD-Integrator libraries2024-03-14T13:03:05Zdockx thibault[Orchestrator] - Adapt CI to integrate new FD-Integrator libraries[Orchestrator] - Adapt CI to integrate new FD-Integrator libraries[Orchestrator] - Adapt CI to integrate new FD-Integrator librariesdockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fusiondirectory-orchestrator/-/issues/35[Orchestrator] - Moving Rest library out to FD-integrator.2024-03-14T13:02:46Zdockx thibault[Orchestrator] - Moving Rest library out to FD-integrator.[Orchestrator] - Moving Rest library out to FD-integrator.
autoload will require the following line :
`require '/usr/share/php/FusionDirectory/autoloader.php';`
renaming the binary to fusiondirectory-orchestrator-client and move it to...[Orchestrator] - Moving Rest library out to FD-integrator.
autoload will require the following line :
`require '/usr/share/php/FusionDirectory/autoloader.php';`
renaming the binary to fusiondirectory-orchestrator-client and move it to Tools repository.dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/user-manual/-/issues/247[Orchestrator] - Adapt CI to integrate new FD-Integrator libraries2024-03-14T10:08:33Zdockx thibault[Orchestrator] - Adapt CI to integrate new FD-Integrator libraries[Orchestrator] - Adapt CI to integrate new FD-Integrator libraries[Orchestrator] - Adapt CI to integrate new FD-Integrator librariesdockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6311system template error2024-03-12T16:25:54Zemmanuel 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/f0314df8bf4cfcc642341d25dcab2361/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 anyway2024-02-27https://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6315delete server systems delete user manager2024-03-12T16:18:46Zemmanuel 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.4https://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6313[CORE] - Snapshots - review of the current automatic creation logic2024-03-12T16:13:33Zdockx 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/6013Add plugin for WebAuthn2024-03-12T12:11:47ZCôme ChillietAdd plugin for WebAuthnAdd a plugin allowing to declare 2nd factor authentication devices using WebAuthn.Add a plugin allowing to declare 2nd factor authentication devices using WebAuthn.FusionDirectory 1.4bmortierbmortier2022-06-06https://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6088Logout in cas mode make a redirection error2024-03-05T18:03:33ZbmortierLogout in cas mode make a redirection error### Description
When we click on logout in CAS we are not forwark to the cas portail again
### Distribution Name and Version
Debian Buster
### FusionDirectory Version
1.4
### PHP version used
7
### Origin of php packages
Debian ...### Description
When we click on logout in CAS we are not forwark to the cas portail again
### Distribution Name and Version
Debian Buster
### FusionDirectory Version
1.4
### PHP version used
7
### Origin of php packages
Debian repo
### Steps to Reproduce
1. Enable CAS
2. Connect with CAS
3. Logout through CAS
4. The URL look like "http://fd.example.com/index.php?signout=1&ticket=ST-6fd6710d15749e5d7f51e9813043d718" but the browser said it's miss redirect
Maybe https://apereo.github.io/cas/4.2.x/installation/Logout-Single-Signout.html can help.
**Expected behavior:**
Redirect on CAS portail URL (auth.example.com in my case)
**Actual behavior:**
Redirect error by the browser
**Reproduces how often:**
100%FusionDirectory 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fusiondirectory-orchestrator/-/issues/34[Orchestrator] - Allows usage of less secure HTTP if configuration file is se...2024-02-27T16:26:15Zdockx thibault[Orchestrator] - Allows usage of less secure HTTP if configuration file is set without HTTP(s)[Orchestrator] - Allows usage of less secure HTTP if configuration file is set without HTTP(s)
Currently, HTTPS is forced. It is better to let the use decide their configuration.[Orchestrator] - Allows usage of less secure HTTP if configuration file is set without HTTP(s)
Currently, HTTPS is forced. It is better to let the use decide their configuration.dockx thibaultdockx thibaulthttps://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/user-manual/-/issues/243remove the dashboard part as is no longer in FusionDirectory2024-02-24T11:03:26Zbmortierremove the dashboard part as is no longer in FusionDirectoryHello,
we need to remove the dashboard part has it's not in FusionDirectory anymore
CheersHello,
we need to remove the dashboard part has it's not in FusionDirectory anymore
CheersFusionDirectory 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fusiondirectory-tools/-/issues/55Update the readme.md2024-02-23T20:17:28ZbmortierUpdate 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/fusiondirectory-integrator/-/issues/25Update the readme.md2024-02-23T20:06:50ZbmortierUpdate 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/fusiondirectory-integrator/-/issues/20align the ci on fusiondirectory and take care of the new dev only branch2024-02-23T19:28:01Zbmortieralign the ci on fusiondirectory and take care of the new dev only branchalign the ci on fusiondirectory and take care of the new dev only branch
Hello,
now that we only have a dev branch we should align and make the ci more simple
Cheersalign the ci on fusiondirectory and take care of the new dev only branch
Hello,
now that we only have a dev branch we should align and make the ci more simple
CheersFusionDirectory Integrator 1.1bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fusiondirectory-integrator/-/issues/21add gihub issues and funding2024-02-23T19:27:28Zbmortieradd gihub issues and fundingHello,
we miss the gihub issues and funding.yml
CheersHello,
we miss the gihub issues and funding.yml
CheersFusionDirectory Integrator 1.1bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fusiondirectory-integrator/-/issues/23add a security.md file2024-02-23T19:21:06Zbmortieradd a security.md fileHello,
we need to add a security.md file
CheersHello,
we need to add a security.md file
CheersFusionDirectory Integrator 1.1bmortierbmortier