fusiondirectory issueshttps://gitlab.fusiondirectory.org/groups/fusiondirectory/-/issues2023-10-03T12:35:32Zhttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6289[Core] - LDAP search methods are triggered when user is created reporting an ...2023-10-03T12:35:32Zdockx thibault[Core] - LDAP search methods are triggered when user is created reporting an error within logs### Description
[Core] - LDAP search methods are triggered when user is created reporting an error within logs
### Distribution Name and Version
Debian 11
### FusionDirectory Version
Repo
### PHP version used
7.4
### Origin of ph...### Description
[Core] - LDAP search methods are triggered when user is created reporting an error within logs
### Distribution Name and Version
Debian 11
### FusionDirectory Version
Repo
### PHP version used
7.4
### Origin of php packages
Repo
### Steps to Reproduce
Simply create a new user and inspect syslog
**Expected behavior:**
No error
**Actual behavior:**
**Jul 3 06:30:31 debian11-fd-vm slapd[2691]: conn=1049 op=2 do_search: invalid dn: "new"**
Jul 3 06:30:31 debian11-fd-vm php: FusionDirectory [fd-admin]: (create) uid=thibault,ou=people,dc=nodomain of type plugin/user objectClass,cn,sn,givenName,uid,userPassword: Success
Jul 3 06:30:31 debian11-fd-vm php: FusionDirectory [fd-admin]: (create) uid=thibault,ou=people,dc=nodomain of type plugin/userRoles objectClass: Success
**Reproduces how often:**
100%
### Additional Information
Does not occur on groups / departments or others save such as tasks.
Seems focused on Users creation.FusionDirectory 1.4.1dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/6240The base where the objects are created with public-form must be written in a ...2023-06-25T21:21:37ZJonathan SwaelensThe base where the objects are created with public-form must be written in a DN formatHello @tdockx @bmortier
The creation base for public-forms must be written in a DN format. It is possible to use a base selector, like for the rest? I think it would be more logical and easy than checking for the DN. I don't see any re...Hello @tdockx @bmortier
The creation base for public-forms must be written in a DN format. It is possible to use a base selector, like for the rest? I think it would be more logical and easy than checking for the DN. I don't see any reason that using a DN would be better than a department.
CheersFusionDirectory 1.4.1bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/6239Private form is not displayed if we only install public-form plugin without i...2023-06-25T21:19:20ZJonathan SwaelensPrivate form is not displayed if we only install public-form plugin without invitationHello @bmortier @tdockx
I see that part in the code of public-forms
```
if (!isset($this->registration) && isset($this->form['fdPublicFormPrivate']) && ($this->form['fdPublicFormPrivate'] == 'TRUE')) {
// Private form and no...Hello @bmortier @tdockx
I see that part in the code of public-forms
```
if (!isset($this->registration) && isset($this->form['fdPublicFormPrivate']) && ($this->form['fdPublicFormPrivate'] == 'TRUE')) {
// Private form and no token
throw new FusionDirectoryException(sprintf(_('Form "%s" is private and requires an invitation'), $this->form['cn']));
}
```
It sounds like the private form is not just another php file but that the whole process if different. It's written somewhere why it is different, exactly? Maybe it would be a nice addition to have for public-form 2 php file so it would be possible to have one or others protected with a portal?FusionDirectory 1.4.1bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6288Make password mandatory based on hash method2023-10-03T12:39:12ZJonathan SwaelensMake password mandatory based on hash methodHello @tdockx
The password is not mandatory by default, it can be seen if we make a template and set the hash method to ssha for example.
There is no `*`. It would be better if we can set it as mandatory based on the hash method.
Righ...Hello @tdockx
The password is not mandatory by default, it can be seen if we make a template and set the hash method to ssha for example.
There is no `*`. It would be better if we can set it as mandatory based on the hash method.
Right now the workaround is to use an `%askme%` macro.
What do you think @bmortier ?FusionDirectory 1.4.1dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6287Change version to 1.4-fixes2023-10-03T12:37:39ZbmortierChange version to 1.4-fixesHello,
we need to change the version to 1.4-fixes
CheersHello,
we need to change the version to 1.4-fixes
CheersFusionDirectory 1.4.1bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/user-manual/-/issues/219[user-manual] - updates supann-ext documentation2023-06-23T18:36:46Zdockx thibault[user-manual] - updates supann-ext documentationIt seems the documentation is incorrect or pointing towards non valid pages.
https://fusiondirectory-user-manual.readthedocs.io/en/1.4/fusiondirectory/plugins/supann-ext/installation.html#install-schemasIt seems the documentation is incorrect or pointing towards non valid pages.
https://fusiondirectory-user-manual.readthedocs.io/en/1.4/fusiondirectory/plugins/supann-ext/installation.html#install-schemasFusionDirectory 1.4dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/6237Add requiredAttrs array to the webservice informations2023-06-11T21:01:05ZJonathan SwaelensAdd requiredAttrs array to the webservice informationsHello @tdockx
The modification helps to know for each section which attrs are mandatory, for example
```
$ C /types/USER/user
{
"sections": {
"perso": {
"name": "Personal information",
"icon": "geticon.php?context=ty...Hello @tdockx
The modification helps to know for each section which attrs are mandatory, for example
```
$ C /types/USER/user
{
"sections": {
"perso": {
"name": "Personal information",
"icon": "geticon.php?context=types&icon=user&size=16",
"attrs": [
"cn",
"sn",
"givenName",
"initials",
"description",
"jpegPhoto"
],
"requiredAttrs": [
"sn",
"givenName"
]
},
"contact": {
"name": "Organizational contact information",
"icon": "geticon.php?context=types&icon=contact&size=16",
"attrs": [
"l",
"st",
"postalAddress",
"roomNumber",
"telephoneNumber",
"mobile",
"pager",
"facsimileTelephoneNumber",
"labeledURI"
],
"requiredAttrs": []
},
"account": {
"name": "Account information",
"icon": "geticon.php?context=applications&icon=ldap&size=16",
"attrs": [
"base",
"uid",
"preferredLanguage",
"userPassword"
],
"requiredAttrs": [
"uid"
]
},
"homecontact": {
"name": "Personal contact information",
"icon": "geticon.php?context=types&icon=contact&size=16",
"attrs": [
"displayName",
"homePostalAddress",
"homePhone"
],
"requiredAttrs": []
},
"organization": {
"name": "Organizational information",
"icon": "geticon.php?context=places&icon=folder&size=16",
"attrs": [
"title",
"o",
"ou",
"departmentNumber",
"employeeNumber",
"employeeType",
"manager"
],
"requiredAttrs": []
}
},
"sections_order": [
"perso",
"contact",
"account",
"homecontact",
"organization"
]
}
```
There will be cases like userPassword that will see as not mandatory because the attribute is not set as required.FusionDirectory 1.5dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6285[Core] - Logic behind account lock must be revised2023-10-03T12:37:59Zdockx thibault[Core] - Logic behind account lock must be revised[Core] - Logic behind account lock must be revised
When putting an account to a deactivate state, by default it deactivates the attribute userPassword by modifying the hash.
This is spread and updated among multiple LDAPs putting other...[Core] - Logic behind account lock must be revised
When putting an account to a deactivate state, by default it deactivates the attribute userPassword by modifying the hash.
This is spread and updated among multiple LDAPs putting other services such as email into a "non-usable" state.
Other services could be impacted as well. In case the account must be deactivated, emails can / might still be available if required.
The full logic behind the locking / deactivation mechanism must be revisited.FusionDirectory 1.5dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fusiondirectory-tools/-/issues/40[Tools] Fusiondirectory-plugin-manager - a yaml verification should happens b...2024-01-18T11:33:15Zdockx thibault[Tools] Fusiondirectory-plugin-manager - a yaml verification should happens before any further processA verification of the overall structure of the yaml and passed arguments should be verified before any process.
In case of error (typo in the yaml E.g) - it should be mentioned before any further processing.
Example of typo but code i...A verification of the overall structure of the yaml and passed arguments should be verified before any process.
In case of error (typo in the yaml E.g) - it should be mentioned before any further processing.
Example of typo but code is executed properly anyway :
```
root@fce0d042bb7d:/home# fusiondirectory-plugins-manager --remove-plugin aida-freediving
aida-freediving plugin has been successfully unregistered.
PHP Notice: Undefined index: fileList in /usr/share/php/FusionDirectory/FusionDirectory/Tools/PluginsManager.php on line 415
PHP Warning: Invalid argument supplied for foreach() in /usr/share/php/FusionDirectory/FusionDirectory/Tools/PluginsManager.php on line 415
unlink: /etc/fusiondirectory/yaml/aida-freediving/description.yaml
```FusionDirectory Tools 1.2dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6279Add hyperlink on plugin URL in plugin dashboard2023-05-25T10:35:11ZcoudotAdd hyperlink on plugin URL in plugin dashboardIt would be better to have an hyperlink (with target="_blank") on plugin manager in dashboard (attribute `fdPluginManagerSupportHomeUrl`).
The code is in `plugins/addons/dashboard/class_dashboardPasswords.inc`:
```php
while ($plugin...It would be better to have an hyperlink (with target="_blank") on plugin manager in dashboard (attribute `fdPluginManagerSupportHomeUrl`).
The code is in `plugins/addons/dashboard/class_dashboardPasswords.inc`:
```php
while ($plugin = $ldap->fetch()) {
$fields = [
['string' => $plugin['cn'][0]],
['string' => $plugin['description'][0]],
['string' => $plugin['fdPluginManagerInfoVersion'][0]],
['string' => $plugin['fdPluginManagerInfoAuthors'][0]],
['string' => $plugin['fdPluginManagerInfoStatus'][0]],
['string' => $plugin['fdPluginManagerInfoOrigin'][0]],
['string' => $plugin['fdPluginManagerSupportProvider'][0]],
['string' => $plugin['fdPluginManagerSupportHomeUrl'][0]],
];
```
I don't know what can be set instead of `string` to have a link.https://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/6231Give the ability to the webservice to notice if an attribute is monovalued or...2023-05-18T13:55:07ZJonathan SwaelensGive the ability to the webservice to notice if an attribute is monovalued or multivaluedHello @tdockx
I modified the rest.php so that it will add to the types endpoint a `""` or `[]` for each attribute.
It can help to notice the type without check FD interface.
Exemple of the output
```
$ C /types/user/supannAccount
{
...Hello @tdockx
I modified the rest.php so that it will add to the types endpoint a `""` or `[]` for each attribute.
It can help to notice the type without check FD interface.
Exemple of the output
```
$ C /types/user/supannAccount
{
"sections": {
"identity": {
"name": "Identity",
"attrs": {
"supannCivilite": "",
"supannAliasLogin": "",
"eduPersonPrincipalName": "",
"eduPersonNickname": "",
"supannRefId": []
}
},
"contact": {
"name": "Contact",
"attrs": {
"supannAutreTelephone": [],
"supannTelephonePrive": [],
"supannAutreMail": [],
"supannMailPerso": [],
"supannMailPrive": [],
"supannAdressePostalePrivee": [],
"supannListeRouge": "",
"mailForwardingAddress": ""
}
},
"affectation": {
"name": "Assignment",
"attrs": {
"supannEntiteAffectationPrincipale": "",
"supannEntiteAffectation": [],
"supannTypeEntiteAffectation": []
}
},
"affiliation": {
"name": "Affiliation",
"attrs": {
"eduPersonPrimaryAffiliation": "",
"eduPersonAffiliation": [],
"supannEtablissement": [],
"supannParrainDN": ""
}
},
"student": {
"name": "Student profile",
"attrs": {
"supannCodeINE": "",
"supannEtuId": ""
}
},
"student2": {
"name": "Student registrations",
"class": [
"fullwidth"
],
"template": "/usr/share/fusiondirectory/plugins/personal/supann/student_subscription.tpl",
"attrs": {
"supannEtuAnneeInscription": "",
"supannEtuRegimeInscription": "",
"supannEtuSecteurDisciplinaire": "",
"supannEtuTypeDiplome": "",
"supannEtuCursusAnnee": "",
"supannEtuDiplome": "",
"supannEtuEtape": "",
"supannEtuElementPedagogique": "",
"supannEtuInscription": ""
}
},
"personnal": {
"name": "Personal profile",
"attrs": {
"supannEmpId": "",
"supannEmpCorps": "",
"supannActivite": []
}
},
"personnal2": {
"name": "Roles",
"class": [
"fullwidth"
],
"attrs": {
"supannRoleGenerique": "",
"supannRoleEntite": ""
}
},
"consentement": {
"name": "Consent",
"class": [
"fullwidth"
],
"attrs": {
"supannConsentement": ""
}
}
},
"sections_order": [
"identity",
"contact",
"affectation",
"affiliation",
"student",
"student2",
"personnal",
"personnal2",
"consentement"
]
}
```FusionDirectory 1.5dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/6223PHP Errors on login2023-04-24T13:44:14ZJrmGrltPHP Errors on login### Description
I can successfully login into my instance but I got several errors with debug flag enabled in fusiondirectory.conf.
### Distribution Name and Version
Debian GNU/Linux 11 (bullseye)
### FusionDirectory Version
Package...### Description
I can successfully login into my instance but I got several errors with debug flag enabled in fusiondirectory.conf.
### Distribution Name and Version
Debian GNU/Linux 11 (bullseye)
### FusionDirectory Version
Package: fusiondirectory
Version: 1.3.1-1
APT-Sources: https://public.fusiondirectory.org/buster-fusiondirectory-release buster/main amd64 Packages
### PHP version used
PHP 7.4.33
### Origin of php packages
APT-Sources: http://ftp.debian.org/debian bullseye/main amd64 Packages
### Steps to Reproduce
1. Install fusiondirectory
2. Enable logging flag and set debug level to something higher than 0
3. Login
4. See php daemon logs
**Expected behavior:**
No php error
**Actual behavior:**
```
Apr 24 17:32:01 myldap php: FusionDirectory [testuser]: (view) error: PHP error: count(): Parameter must be an array or an object that implements Countable(/apps/ldap/fusiondirectory/www/include/class_config.inc, line 646)
Apr 24 17:32:01 myldap php: FusionDirectory [testuser]: (view) error: PHP error: count(): Parameter must be an array or an object that implements Countable(/apps/ldap/fusiondirectory/www/include/class_config.inc, line 646)
Apr 24 17:32:01 myldap php: FusionDirectory [testuser]: (view) error: PHP error: count(): Parameter must be an array or an object that implements Countable(/apps/ldap/fusiondirectory/www/include/class_config.inc, line 646)
Apr 24 17:32:01 myldap php: FusionDirectory [testuser]: (view) error: PHP error: count(): Parameter must be an array or an object that implements Countable(/apps/ldap/fusiondirectory/www/include/class_config.inc, line 646)
Apr 24 17:32:01 myldap php: FusionDirectory [testuser]: (view) error: PHP error: count(): Parameter must be an array or an object that implements Countable(/apps/ldap/fusiondirectory/www/include/class_config.inc, line 646)
Apr 24 17:32:01 myldap php: FusionDirectory [testuser]: (view) error: PHP error: count(): Parameter must be an array or an object that implements Countable(/apps/ldap/fusiondirectory/www/include/class_config.inc, line 646)
Apr 24 17:32:01 myldap php: FusionDirectory [testuser]: (view) error: PHP error: count(): Parameter must be an array or an object that implements Countable(/apps/ldap/fusiondirectory/www/include/class_config.inc, line 646)
Apr 24 17:32:01 myldap php: FusionDirectory [testuser]: (view) error: PHP error: count(): Parameter must be an array or an object that implements Countable(/apps/ldap/fusiondirectory/www/include/class_config.inc, line 646)
Apr 24 17:32:01 myldap php: FusionDirectory [testuser]: (view) error: PHP error: count(): Parameter must be an array or an object that implements Countable(/apps/ldap/fusiondirectory/www/include/class_config.inc, line 646)
Apr 24 17:32:01 myldap php: FusionDirectory [testuser]: (view) error: PHP error: count(): Parameter must be an array or an object that implements Countable(/apps/ldap/fusiondirectory/www/include/class_config.inc, line 646)
Apr 24 17:32:01 myldap php: FusionDirectory [testuser]: (view) error: PHP error: count(): Parameter must be an array or an object that implements Countable(/apps/ldap/fusiondirectory/www/include/class_config.inc, line 646)
Apr 24 17:32:01 myldap php: FusionDirectory [testuser]: (view) error: PHP error: count(): Parameter must be an array or an object that implements Countable(/apps/ldap/fusiondirectory/www/include/class_config.inc, line 646)
Apr 24 17:32:01 myldap php: FusionDirectory [testuser]: (view) error: PHP error: count(): Parameter must be an array or an object that implements Countable(/apps/ldap/fusiondirectory/www/include/class_config.inc, line 646)
Apr 24 17:32:01 myldap php: FusionDirectory [unauthenticated]: (view) error: PHP error: readfile(): Filename cannot be empty(/apps/ldap/fusiondirectory/www/html/geticon.php, line 51)
```
**Reproduces how often:**
Each login
### Additional Information
I used official fd package installed in a custom directory
Iam using Apache/2.4.56bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fusiondirectory-integrator/-/issues/15Add exceptions for ldap library2023-04-24T15:34:45ZJonathan SwaelensAdd exceptions for ldap libraryHello,
The error are not clear and display a trace.
It will be better to have proper messages
```
root@defd9c121ed2:/# fusiondirectory-plugins-manager --unregister-plugin /etc/fusiondirectory/yaml/systems/description.yaml
Error while...Hello,
The error are not clear and display a trace.
It will be better to have proper messages
```
root@defd9c121ed2:/# fusiondirectory-plugins-manager --unregister-plugin /etc/fusiondirectory/yaml/systems/description.yaml
Error while deleting branch : /etc/fusiondirectory/yaml/systems/description.yaml !
PHP Fatal error: Uncaught FusionDirectory\Ldap\Exception: No such object (32)(matched dn: ou=pluginManager,dc=nodomain) in /usr/share/php/FusionDirectory/FusionDirectory/Ldap/Result.php:117
Stack trace:
#0 /usr/share/php/FusionDirectory/FusionDirectory/Tools/PluginsManager.php(261): FusionDirectory\Ldap\Result->assert()
#1 [internal function]: FusionDirectory\Tools\PluginsManager->deletePluginRecord('/etc/fusiondire...')
#2 /usr/share/php/FusionDirectory/FusionDirectory/Cli/Application.php(198): call_user_func(Array, Array)
#3 /usr/share/php/FusionDirectory/FusionDirectory/Tools/PluginsManager.php(118): FusionDirectory\Cli\Application->runCommands()
#4 /usr/sbin/fusiondirectory-plugins-manager(29): FusionDirectory\Tools\PluginsManager->run(Array)
#5 {main}
thrown in /usr/share/php/FusionDirectory/FusionDirectory/Ldap/Result.php on line 117
```FusionDirectory Integrator 1.1dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/user-manual/-/issues/209Document proprerly the lastest version of the FusionDirectory Tools2023-09-28T20:24:21ZJonathan SwaelensDocument proprerly the lastest version of the FusionDirectory ToolsHello fusiondirectory-plugins-manager --unregister-plugin doesn't have an example.
It use the plugin name right now, it will be useful to have one visible example
```
root@defd9c121ed2:/# fusiondirectory-plugins-manager --unregister-...Hello fusiondirectory-plugins-manager --unregister-plugin doesn't have an example.
It use the plugin name right now, it will be useful to have one visible example
```
root@defd9c121ed2:/# fusiondirectory-plugins-manager --unregister-plugin systems
Deleted systems from LDAP successfully.
```FusionDirectory 1.4bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fusiondirectory-tools/-/issues/25Migrate users function doesn't work when it try to convert person objectclass...2024-01-22T09:11:22ZbmortierMigrate users function doesn't work when it try to convert person objectclass to inetorgpersonI have an ldif like this one
```
root@c79e4a2e781a:/# ldapsearch -xLLL -H ldap://localhost -b dc=nodomain uid=tata1
dn: uid=tata1,dc=nodomain
cn: tata
sn: toto
uid: tata1
objectClass: person
objectClass: posixAccount
uidNumber: 1001
gid...I have an ldif like this one
```
root@c79e4a2e781a:/# ldapsearch -xLLL -H ldap://localhost -b dc=nodomain uid=tata1
dn: uid=tata1,dc=nodomain
cn: tata
sn: toto
uid: tata1
objectClass: person
objectClass: posixAccount
uidNumber: 1001
gidNumber: 1001
homeDirectory: /
```
When I use the command to migrate the users it fails
```
root@c79e4a2e781a:/# fusiondirectory-migration-manager --migrate-users
The following users are missing objectClasses:
uid=tata1,dc=nodomain
Add the inetOrgPerson objectClass to all these entries? [Yes/No]?
yes
Failed to modify entry "uid=tata1,dc=nodomain": structural object class modification from 'person' to 'inetOrgPerson' not allowed (69)
```FusionDirectory Tools 1.2dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6256Rename user entry2023-02-03T08:58:08ZbmortierRename user entry## Rename user entry
### Actual behavior
When editing a user, the login/uid field is not editable.
### Expected behavior
It would be nice to allow people to rename a user entry, through global configuration (allow it or not) and ACL ...## Rename user entry
### Actual behavior
When editing a user, the login/uid field is not editable.
### Expected behavior
It would be nice to allow people to rename a user entry, through global configuration (allow it or not) and ACL (allow it only for certain roles)
It should remain forbidden by default to keep current behavior.
### Benefits
This is needed for one of our client that is not "comfortable" doing so in ADS while renaming entry is well supported by his LDAP client apps, as they use the entryUUID attribute instead of uid to map their internal user with LDAP user, thus allowing changing the uid without loosing the user application data.bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/6205[Zimbra] - Lifecycle of Zimbra account - Errors of re-activation and auto-act...2023-06-27T09:54:49Zdockx thibault[Zimbra] - Lifecycle of Zimbra account - Errors of re-activation and auto-activation not working.### Description
[Zimbra] - Lifecycle of Zimbra account - Errors of re-activation and auto-activation not working.
### Distribution Name and Version
Debian 11
### FusionDirectory Version
FD 1.4
### Plugin with the defect
Soap Zimbra...### Description
[Zimbra] - Lifecycle of Zimbra account - Errors of re-activation and auto-activation not working.
### Distribution Name and Version
Debian 11
### FusionDirectory Version
FD 1.4
### Plugin with the defect
Soap Zimbra
### PHP version used
7.4
### Origin of php packages
Distro
### Steps to Reproduce
1. If an FD account is disabled the Zimbra account is disabled but if the FD account is re-enabled to Zimbra account remains disabled.
2. Upon any modification on an account referenced within FusionDirectory, any updates even a simple apply makes the Zimbra account activated again.
3. There seems to be strange behavior between automatic and manual fulfilling of the Zimbra page. Automating is not working.
**Expected behavior:**
Expected positive output from the three bullets points mentioned above.
**Actual behavior:**
Described within the steps.
**Reproduces how often:**
100 %
### Additional Information
See more information on the ticket open by the customer.FusionDirectory 1.5dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6252add attribute values in the audit logs2023-01-30T10:14:36Zbmortieradd attribute values in the audit logs### Requirements
it requires new config attributes in fusion directory schema
## Descriptive title for this enhancement
When making an action on any entry, the values are not logged in the audit logs.
It could be interesting to have ...### Requirements
it requires new config attributes in fusion directory schema
## Descriptive title for this enhancement
When making an action on any entry, the values are not logged in the audit logs.
It could be interesting to have the details of the action. For example:
```
Object Values: add:description=foo
Object Values: replace:cn=bar
Object Values: delete:l
```
### Current behavior
No value logged in the audit logs
### Expected behavior
Values logged in the audit logs, in case of `changetype: add` or `changetype: modify`
For `changetype: modify`, we should also log if the attribute has been deleted / replaced / added.
### Benefits
Better audit logging
### Possible Drawbacks
Consume much more data in LDAP. Maybe we should have an option to enable / disable value logging.FusionDirectory 1.5bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6251audit the lock / unlock actions2023-01-31T17:46:30Zbmortieraudit the lock / unlock actions
## Descriptive title for this enhancement
Currently, it seems there is no audit log for "lock / unlock" actions. (even in security action types)
It would be nice to have these logs, maybe as a "security" action type.
### Actual behavi...
## Descriptive title for this enhancement
Currently, it seems there is no audit log for "lock / unlock" actions. (even in security action types)
It would be nice to have these logs, maybe as a "security" action type.
### Actual behavior
Nothing appears in the audit logs
### Expected behavior
A new log entry for each lock/unlock action
### Benefits
* more audit logs
### Possible Drawbacks
* /FusionDirectory 1.5bmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/6204[Samba] - Samba domain is wrongly behaving when configured in the backend as ...2023-01-24T12:10:36Zdockx thibault[Samba] - Samba domain is wrongly behaving when configured in the backend as well as within the plugin.### Description
It seems there is a double employment of the backend config with samba object domain managed within FD.
### Distribution Name and Version
Debian 11
### FusionDirectory Version
1.4
### Plugin with the defect
Samba
...### Description
It seems there is a double employment of the backend config with samba object domain managed within FD.
### Distribution Name and Version
Debian 11
### FusionDirectory Version
1.4
### Plugin with the defect
Samba
### PHP version used
7.4
### Origin of php packages
Distros
### Steps to Reproduce
Configure a domain in the backend configuration.
Apply it within the plugin tab for a specific user.
Default + new domain name setup should appear and it is not always the case.
**Expected behavior:**
Domains configured should be listed as well as default.
**Actual behavior:**
Only the domain configured seems to appears.
(To be confirmed here).
**Reproduces how often:**
To be confirmed.
### Additional Information
<!-- optional -->
<!-- Any additional information, configuration or data that might be necessary to reproduce the issue. -->FusionDirectory 1.5dockx thibaultdockx thibault