fusiondirectory-plugins issueshttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues2024-03-28T11:09:02Zhttps://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-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-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-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-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-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/6244[Public-form] - Allow usage of private form without plugin invitation installed2023-10-02T14:28:17Zdockx thibault[Public-form] - Allow usage of private form without plugin invitation installed[Public-form] - Allow usage of private form without plugin invitation installed
In the context of an SP (Service Provider), the IDP (Identity Provider) authenticate the user but the SP requires local registration of such users in order ...[Public-form] - Allow usage of private form without plugin invitation installed
In the context of an SP (Service Provider), the IDP (Identity Provider) authenticate the user but the SP requires local registration of such users in order to manage required applications access.
The SP therefore issue a "private-form" allowing headers sent by the IDP to fill-in presented fields of the form.
Private-form, as of today, requires invitations plugin and is mandate to verify tokens.
For the SP, a token is now required and an "invitation" is not mandatory. Rending the plugin invitations obsolete but the private-form unsuable due to lack of tokens.
The MR should resolve this problems by adding a "backend configuration" boolean field, allowing the usage of private-form without the plugins invitation installed.FusionDirectory 1.5dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/6242Public form must be able to create locked users by default2023-08-25T10:20:32ZJonathan SwaelensPublic form must be able to create locked users by defaultPublic form must be able to create locked users by default.
Right now it's created but without any lock.
It would be nice to be able to tick an option to lock it at creation.Public form must be able to create locked users by default.
Right now it's created but without any lock.
It would be nice to be able to tick an option to lock it at creation.FusionDirectory 1.5dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/6241Private form must not be related to the plugin invitations2023-11-16T16:33:39ZJonathan SwaelensPrivate form must not be related to the plugin invitationsPrivate form must not be related to the plugin invitations.
The code must be read and see the differences again between private / public formPrivate form must not be related to the plugin invitations.
The code must be read and see the differences again between private / public formFusionDirectory 1.5dockx 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-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/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-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 thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/6203[Supann-Ex] - Verification of uniqueness, generation of hash based on login I...2023-01-26T14:22:02Zdockx thibault[Supann-Ex] - Verification of uniqueness, generation of hash based on login ID and time.### Requirements
* Filling out the template is required. Any Enhancement request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
* All new code requires tests to e...### Requirements
* Filling out the template is required. Any Enhancement request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
* All new code requires tests to ensure against regressions
## Descriptive title for this enhancement
[Supann-Ex] - Verification of uniqueness, generation of hash based on login ID and time.
### Actual behavior
If the number of users exceed a certain value, we see a huge impact on performances due to the iteration on each individual.
This was performed in order to make sure of the uniqueness between members.
It is now seen as unpractical and a revamp of the solution is required.
The hash must be generated with the ID of the user as well as the time of creation.
### Expected behavior
No need to pass by every entry in LDAP in order to validated uniqueness.
The hash is generated in a way that it is "almost" impossible to replicate.
### Step by step description of new behaviour
1. New hash generation.
2. Better LDAP performances.
### Benefits
Huge benefits in terms of performances.
### Possible Drawbacks
None
### Applicable Issues
https://gitlab.fusiondirectory.org/universite-orleans/mise-en-place-de-fusiondirectory-et-openldap/-/issues/26#note_117328FusionDirectory 1.5dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/6198[Renater-Partage] - Implementation of mailbox account status within user tab.2023-01-26T14:39:45Zdockx thibault[Renater-Partage] - Implementation of mailbox account status within user tab.### Requirements
**New Features**
*New mail account status within User, Mail Tab*
```
zimbraAccountStatus
String(active, closed, locked, lockout, pending, maintenance).
```
## Descriptive title for this enhancement
We decided i...### Requirements
**New Features**
*New mail account status within User, Mail Tab*
```
zimbraAccountStatus
String(active, closed, locked, lockout, pending, maintenance).
```
## Descriptive title for this enhancement
We decided it would be very useful to unlock / lock or simply select the proper status of the mailbox directly from the user interface.
### Actual behavior
There are no features allowing manual change of the status of the mailbox account status directly.
The only way working today is if the account already exists in Renater-Partage and is locked, a setting within FD allows the re-activation of that account during creation within LDAP.
### Expected behavior
A simple menu allowing to update the status of the mailbox for the current user selected.
### Step by step description of new behavior
* select the user
* open the mail tab
* select the status of the account
* Upon save or apply, the account status is modified within LDAP and Partage.
### Benefits
If an account is currently locked within Partage, we only see the status within FD.
It would now be beneficial to allow its modification as well.
### Possible Drawbacks
None perceived.
### Applicable Issues
None.FusionDirectory 1.5dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/6190[WebService] - RPCservice - Verification on session timeout, possible unecess...2022-12-07T10:15:13Zdockx thibault[WebService] - RPCservice - Verification on session timeout, possible unecessary refresh.### Requirements
The university of Unamur reported some issue during movement / copy / creation of many users via the use of FD WebService.
It is possible that one part of the issue would be the creation of a new session which would be...### Requirements
The university of Unamur reported some issue during movement / copy / creation of many users via the use of FD WebService.
It is possible that one part of the issue would be the creation of a new session which would be not efficient.
## Descriptive title for this enhancement
[WebService] - RPCservice - Verification on session timeout, possible unecessary refresh.
### Actual behavior
It seems a big delay of around 2 minutes per request process during user modification / creation happens.
Making the overall life cycle process difficult to complete.
### Expected behavior
Delay between such request should be fast.
### Step by step description of new behaviour
A possible tweak of session management and timeout could help fix this behaviour.
### Benefits
Life cycle / user creation - suppression would be processed within a reasonable timeframe.
### Possible Drawbacks
None.
### Applicable IssuesFusionDirectory 1.5dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/6189[REST] Entry with "/" in their RDN cannot be managed by REST webservice2023-07-28T13:04:48Zsfroger[REST] Entry with "/" in their RDN cannot be managed by REST webservice### Description
Using webservice REST (https://rest-api.fusiondirectory.org/) on FD 1.4, it's impossible to read or update objects whose RDN have "/" in them, such as supannEntity.
### Distribution Name and Version
Any
### FusionDire...### Description
Using webservice REST (https://rest-api.fusiondirectory.org/) on FD 1.4, it's impossible to read or update objects whose RDN have "/" in them, such as supannEntity.
### Distribution Name and Version
Any
### FusionDirectory Version
latest 1.4 dev branch
### Plugin with the defect
webservice
### PHP version used
7.4.3
### Steps to Reproduce
Call webservice using curl to get a token
```
export FD_TOKEN=$(curl -X POST -d '{"directory": "default", "user": "fd-admin", "password": "secret"}' http://<fd.local>/rest.php/v1/login | sed 's/"//g')
```
Try to read entry containing two "/" in RDN
```
curl -H "Session-Token: $FD_TOKEN" http://<fd.local>/rest.php/v1/objects/ENTITE/supannCodeEntite=DC/DAF/PDC,ou=structures,dc=domain,dc=com
```
Getting error:
```
[{"class":"WebServiceError","message":"Tab \"DAF\" of type \"ENTITE\" does not exists","line":213,"file":"/usr/local/share/fusiondirectory/include/webservice/class_fdRPCService.inc"}]
```
Try to read entry containing three "/" in RDN:
```
curl -H "Session-Token: $FD_TOKEN" http://<fd.local>/rest.php/v1/objects/ENTITE/supannCodeEntite=DC/SG/PVC/SVE,ou=structures,dc=domain,dc=com
```
Getting error
```
[{"class":"WebServiceError","message":"[endpoint_objects_GET_5] Invalid request for endpoint objects: GET with 5 path elements","line":190,"file":"/usr/local/share/fusiondirectory/html/rest.php"}]
```
I tried to URLencode the "/" in the DN, replacing "/" with %2F with same error, tried escaping with %252f (escaping the %) but got a "Non-existing dn" error.
It seems that even if I could configure the http server to not decode the "/" in the URL transmitted in PATH_INFO (eg. with `AllowEncodedSlashes NoDecode` in Apache), Fusiondirectory doesn't decode it when requesting the DN.
**Expected behavior:**
Be able to manage these entries
**Actual behavior:**
Cannot read or update object.
### Additional Information
A quick fix I've tested would be to decode the DN passed in the URL, so escaping the slashes with "%252f" would work (http server would decode %252f to %2f and %2f would be decoded by Fusiondirectory)FusionDirectory 1.5dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/6188[SupannEx] - Population Code and User reference - Delete on cascade.2022-12-07T10:29:09Zdockx thibault[SupannEx] - Population Code and User reference - Delete on cascade.### Requirements
It is required upon deletion of a Population Code, custom or not. To remove the associated reference for linked users.
Today, upon deletion of such code, the linked users are keeping the value, which is therefore not va...### Requirements
It is required upon deletion of a Population Code, custom or not. To remove the associated reference for linked users.
Today, upon deletion of such code, the linked users are keeping the value, which is therefore not valid within the population code list.
This will return an error upon modification of such users in the future.
## Descriptive title for this enhancement
Brings delete on cascade once a population code is modified or deleted.
### Actual behavior
Code Population and customs codes remains saved within user attributes values and should be removed.
### Expected behavior
Upon deletion of a Population Code, the linked users referenced will delete the Population Code linked as well.
### Step by step description of new behavior
User plForeignKey must be configured for SupannEx Configuration Tab for below attributes:
- supannCodePopulation
### Benefits
Problems won't occur if a user is updated in case Code Population is not existing.
### Possible Drawbacks
None.
### Applicable Issues
None.FusionDirectory 1.5dockx thibaultdockx thibaulthttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/6184[WebService] - LDAP Boolean are returned in lower case while stored in upper ...2022-12-07T10:28:45Zdockx thibault[WebService] - LDAP Boolean are returned in lower case while stored in upper case.### Description
During a retrieval of attributes, values such as "supannListeRouge" which return a boolean.
The boolean attribute value is stored in upper case, while the web service returns lower case.
This seems to be always the cas...### Description
During a retrieval of attributes, values such as "supannListeRouge" which return a boolean.
The boolean attribute value is stored in upper case, while the web service returns lower case.
This seems to be always the case for returned Boolean.
### Distribution Name and Version
Debian 11
### FusionDirectory Version
1.4-dev
### Plugin with the defect
Werb Service
### PHP version used
7.4
### Origin of php packages
Distro packages
### Steps to Reproduce
httpie or Curl on the supannListRouge attribute will return lower case True or False.
**Expected behavior:**
The same return value as stored in LDAP.
Meaning in upper case value.
**Actual behavior:**
Lower case boolean are always returned.
**Reproduces how often:**
100 percent.
### Additional Information
Although this is not the intended output returned by the web service, this has low to none impact on the process.
LSC does not return issues and the data are processed properly.FusionDirectory 1.5dockx thibaultdockx thibault