fusiondirectory-plugins issueshttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues2022-09-01T10:57:18Zhttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/5963error in SINAPS workflow2022-09-01T10:57:18Zagallavardinerror in SINAPS workflow### Description
It seems that Passport send acquisition ( like role deletion) before sending acknowledgment of diffusion
### Distribution Name and Version
Debian
### FusionDirectory Version
1.3.1
### Plugin with the defect
SINAP
##...### Description
It seems that Passport send acquisition ( like role deletion) before sending acknowledgment of diffusion
### Distribution Name and Version
Debian
### FusionDirectory Version
1.3.1
### Plugin with the defect
SINAP
### PHP version used
7
### Origin of php packages
from debian
### Steps to Reproduce
1. a user is expired on sinaps
2. sinaps send a diffusion
3. FD send acquisition
4. FD send acknoledgement of diffusion
**Expected behavior:**
we must have following order
1. sinaps send diffusion
2. FD acknowledge diffusion
3. FD send acquisition
**Reproduces how often:**
no information
### Additional Information
Message of SINAPS support
> De plus, nous constatons au travers des logs que FUSIONDIRECTORY envoie la suppression du rôle EXT de type "AN" avant d'avoir retourné la réponse d'acquittement (synchrone) de la diffusion.
> De fait, la référence croisée FUSIONDIRECTORY est supprimée dans Sinaps et lorsque l'acquittement arrive, il recherche cette référence croisée qui n'existe plus.
> Cela a pour impact de re-créer une ligne dans la table des références croisées pour laquelle la valeur de la colonne "clé primaire de l'objet métier cible" est vide.
> Il est indispensable que les actions soient traitées dans le bon ordre à savoir :
> - d'abord le retour d'acquittement Synchrone de FUSIONDIRECTORY
> - et ensuite seulement l'envoi par FUSIONDIRECTORY à SINAPS de la suppression
> Cela doit être vu côté FUSIONDIRECTORY.FusionDirectory 1.3.1agallavardinagallavardinhttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/5948description of a user should'nt be updated from SINAPS2019-06-28T20:53:42Zagallavardindescription of a user should'nt be updated from SINAPS### Description
Description is updated from sinaps, Finally it isn't a good idea
### Distribution Name and Version
debian
### FusionDirectory Version
1.3.1
### Plugin with the defect
sinaps
### PHP version used
7
### Origin of php pa...### Description
Description is updated from sinaps, Finally it isn't a good idea
### Distribution Name and Version
debian
### FusionDirectory Version
1.3.1
### Plugin with the defect
sinaps
### PHP version used
7
### Origin of php packages
debian
### Steps to Reproduce
1. set a accoutn on Fd with a description
2. Sync the Id( with a blank description from sinaps to FD
**Expected behavior:**
description shouldn't be synced
**Actual behavior:**
description is synced
**Reproduces how often:**
100 %
### Additional Information
remove line 213 inside include/class_sinapsRequest.inc should do the trickFusionDirectory 1.3.1Côme ChillietCôme Chilliethttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/5945unable to add SINAPS Structure2019-06-28T20:53:44Zagallavardinunable to add SINAPS Structure### Description
unabel to add structure, PHP error occurs
### Distribution Name and Version
Debian 9
### FusionDirectory Version
1.3-2~jenkinsbuild113
### Plugin with the defect
fusiondirectory-plugin-sinaps 1.3-2~jenkinsbuild...### Description
unabel to add structure, PHP error occurs
### Distribution Name and Version
Debian 9
### FusionDirectory Version
1.3-2~jenkinsbuild113
### Plugin with the defect
fusiondirectory-plugin-sinaps 1.3-2~jenkinsbuild113
### PHP version used
7
### Origin of php packages
from debian reository
### Steps to Reproduce
1. create structure on sinaps
2. push it on FusionDirectory
**Expected behavior:**
A new structure is create and Id sent to sinaps
**Actual behavior:**
php Error
```
php /usr/share/doc/fusiondirectory-plugin-sinaps/test/testEndPoint.php http://fd-server/sinaps.php?token=991997f4-a48f-4e8d-87e5-78432fbe80ed ./ee67e316-6e9b-4d0a-9935-b8c523ef1db0.xml
***** Server response *****
<br />
<b>Fatal error</b>: Uncaught InvalidValueException: SetAttribute "Parent entities" was set to a non-compatible value in /usr/share/fusiondirectory/include/simpleplugin/attributes/class_SetAttribute.inc:352
Stack trace:
#0 /usr/share/fusiondirectory/include/simpleplugin/class_Attribute.inc(164): SetAttribute->checkValue('DAFA')
#1 /usr/share/fusiondirectory/include/simpleplugin/class_Attribute.inc(643): Attribute->setValue('DAFA')
#2 /usr/share/fusiondirectory/include/simpleplugin/class_simplePlugin.inc(1938): Attribute->deserializeValue('DAFA')
#3 /usr/share/fusiondirectory/include/class_sinapsDiffusionHandlerJob.inc(255): simplePlugin->deserializeValues(Array)
#4 /usr/share/fusiondirectory/include/class_sinapsDiffusionHandlerJob.inc(136): sinapsDiffusionHandlerJob->fillObject('entite', Array, 'supannCodeEntit...')
#5 /usr/share/fusiondirectory/include/class_sinapsDiffusionHandlerJob.inc(59): sinapsDiffusionHandlerJob->handleStructureDiffusion(Array)
#6 /usr/share/fusiondirectory/html/sinaps.php(79): sinapsDiffusionHandlerJob->h in <b>/usr/share/fusiondirectory/include/simpleplugin/attributes/class_SetAttribute.inc</b> on line <b>352</b><br />
***** End of server response *****
```
**Reproduces how often:**
100%
### Additional Information
as attachement xml file and dry-run file
parent structure exist !
[DAFA-G-GEST.DRY-RUN](/uploads/36deb20606ff0bd506235e3a2ba212cd/DAFA-G-GEST.DRY-RUN)
[DAFA-G-GEST.xml](/uploads/4fc605844986f877da9918e0466300aa/DAFA-G-GEST.xml)FusionDirectory 1.3.1Côme ChillietCôme Chilliethttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/5943SINAPS : if contact method are not the same or missing in sinaps , acquisitio...2019-09-24T10:32:38ZagallavardinSINAPS : if contact method are not the same or missing in sinaps , acquisition must be sent### Requirements
## Descriptive title for this enhancement
when diffusion is done, contact method must be compared, if there are different or not exist on SINAPS, acquisition must be done
### Actual behavior
no acquisition is done af...### Requirements
## Descriptive title for this enhancement
when diffusion is done, contact method must be compared, if there are different or not exist on SINAPS, acquisition must be done
### Actual behavior
no acquisition is done after diffusion
### Expected behavior
when diffusion is done, contact method must be compared, if there are different or not exist on SINAPS, acquisition must be done
### Step by step description of new behaviour
1. diffusion is done to Fusion
2. compare contact method from sinaps and Fusion , if different ( incorrect or missing on sinaps side) an acquisition is mandatory
3. lanch acquisition if necesary
### Benefits
coherence between SINAPS an FDCôme ChillietCôme Chilliethttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/5941Error when identity is spread from SINAPS "Cannot delete non-existing user {...2019-06-28T20:53:43ZagallavardinError when identity is spread from SINAPS "Cannot delete non-existing user {LDAPUUID}"### Description
strange error during "diffusion" : spread an identity from SINAPS to FD
on SINAPS side : identity didn't have FD cross-reference
on FD side : account exist (tested with a prefilled LDAPUUID and without a pre filled LDAP...### Description
strange error during "diffusion" : spread an identity from SINAPS to FD
on SINAPS side : identity didn't have FD cross-reference
on FD side : account exist (tested with a prefilled LDAPUUID and without a pre filled LDAPUUID)
### Distribution Name and Version
Debian 9.8
### FusionDirectory Version
1.3 from integration
### Plugin with the defect
fusiondirectory-sinaps 1.3.1 from gz from sources
plugins install with fusiondirectory-setup --plugins
### PHP version used
php 7
### Origin of php packages
from oficiel Deb repos
### Steps to Reproduce
1. spread to FusionDirectory an identity with no cross reference, on FD there a corresponding user ( same sn and givenname) with a pre filled LDAPUUID
2. check the xml-acquittement
**Expected behavior:**
on current installation ( 1.3 ) we have an error like `"The entry 'uid=john.doe,ou=people,ou=site,dc=company,dc=fr' already use this 'Login' attribute!`[b8048447-f719-4c2d-bb9e-b94dffcb9eba.xml](/uploads/b11420c4fffef94d3eaba202edfa62ea/b8048447-f719-4c2d-bb9e-b94dffcb9eba.xml)
[3f646d29-e346-4095-a6b2-ef61d93b6619-acquittement.xml](/uploads/92866486808be5c59da1a705e8e2693e/3f646d29-e346-4095-a6b2-ef61d93b6619-acquittement.xml)
[b8048447-f719-4c2d-bb9e-b94dffcb9eba-acquittement.xml](/uploads/8123fbbf55bdd6ee2cd366849a59dd7d/b8048447-f719-4c2d-bb9e-b94dffcb9eba-acquittement.xml)
[3f646d29-e346-4095-a6b2-ef61d93b6619.xml](/uploads/66049cd6ef10fec811c4563b34f77ff2/3f646d29-e346-4095-a6b2-ef61d93b6619.xml)
**Actual behavior:**
we have the following error :
`Erreur Fonctionnelle - Code réponse 200 : Données pour la transaction 4e5a42f3-7d5e-4146-aad0-87b5f8bb6096 non intégrées - Cannot delete non-existing user {LDAPUUID}e2dda2de-c842-4e8f-8163-d0c174fd4ddc`
If diffusion is done again the LDAPUUID in error message change .
those LDAPUUID didn't exist inside LDAP tree
**Reproduces how often:**
100 % with the same userFusionDirectory 1.3.1Côme ChillietCôme Chilliethttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/5989Remove dependency on POSIX when using Samba42019-11-29T14:02:38ZagallavardinRemove dependency on POSIX when using Samba4* Samba 3 works well with Fd and an external LDAP tree . FD is obliged to maintain a dependency between Posix account and samba Account . OK no problem with it !
* Samba 4 contains is own LDAP directory . From several advice the best way...* Samba 3 works well with Fd and an external LDAP tree . FD is obliged to maintain a dependency between Posix account and samba Account . OK no problem with it !
* Samba 4 contains is own LDAP directory . From several advice the best ways is to create a task to sync internal SAMBA LDAP from FD Ldap with LSC ( for example)(by the way, you could replace Samba 4 per ActiveDirectory)
In the last case, Is it necessary to keep a dependency posix <=> samba tab ?
This dependency is constraining ...
In fact I just want to create an "Microsoft" Identity wich could be done without providing all posix field like uidNumber, Posixnumber home Directory and so one ..
A flag could be done in samba plugin config backend ? ( no idea about consequence , but I guess that is the same problem for group)
Available to discuss on It .FusionDirectory 1.4agallavardinagallavardinhttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/5917flag_ownmailbox cannot be used with partage mail method2019-06-28T20:53:43Zagallavardinflag_ownmailbox cannot be used with partage mail method### Description
### Distribution Name and Version
Debian
### FusionDirectory Version
1.3-2~jenkinsbuild96
### Plugin with the defect
partage
### PHP version used
php7
### Origin of php packages
debian
### Steps to Reproduce
1. c...### Description
### Distribution Name and Version
Debian
### FusionDirectory Version
1.3-2~jenkinsbuild96
### Plugin with the defect
partage
### PHP version used
php7
### Origin of php packages
debian
### Steps to Reproduce
1. create a partage server with cos
2. create a user
3. add a mail account and select the partage server
**Expected behavior:**
We could check or uncheck the "flag_ownmailbox" checkbox ( which is correspond to zimbraPrefMailLocalDeliveryDisabled field)
**Actual behavior:**
At this point the checkbox couldn't be check
**Reproduces how often:**
100%FusionDirectory 1.3.1Côme ChillietCôme Chilliethttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/5913Avoid mass acquistion when editing group gidNumber2019-06-28T20:53:42ZagallavardinAvoid mass acquistion when editing group gidNumber### Requirements
## Descriptive title for this enhancement
### Actual behavior
When a posix group is deleted or modified ( like modified the gidNumber or name ), Fd check consistency on all people which user the posixAccount feature.
...### Requirements
## Descriptive title for this enhancement
### Actual behavior
When a posix group is deleted or modified ( like modified the gidNumber or name ), Fd check consistency on all people which user the posixAccount feature.
By checking consistency of all account and if SINAPS is enabled all account is scanned and corresponding acquisition is sent
I see in log ldap request to get all attribute sent to sinaps
```
Jan 25 10:15:28 mc-pas-test slapd[698]: conn=17763 op=21987 SRCH attr=supannRefId supannEntiteAffectationPrincipale telephoneNumber facsimileTelephoneNumber mail mobi
le dn
```
for one modification I see 382 request
```
root@mc-pas-test:/var/cache/fusiondirectory/tmp# grep " SRCH attr=supannRefId supannEntiteAffectationPrincipale" /var/log/syslog |grep 17763 |wc -l
382
```
which is corresponding to posixuser concerned by the modified group
### Expected behavior
Acquisition is sent only when field specified in fdSinapsAcquisitionContactMethodMap are modified
### Step by step description of new behaviour
1. modify/delete a group
2. as this change didn't concern to sinaps information no acquisition should be launched
### Benefits
group modification more quick
### Possible Drawbacks
code complexity
### additional information
It seems that modification launch other actions like mailbox check ( partage for example)FusionDirectory 1.3.1Côme ChillietCôme Chilliethttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/5911supannRefId field is missing for "etablissement"2021-01-28T21:29:10ZagallavardinsupannRefId field is missing for "etablissement"### Requirements
Add the supannRefId field in FD when adding or modifying an "etablissement"
It is allowed by LDAP schema (field member of supannEntite)
### Actual behavior
![image](/uploads/31d07e7fb6b418351d5cfe2f253b0ea1/image.png)...### Requirements
Add the supannRefId field in FD when adding or modifying an "etablissement"
It is allowed by LDAP schema (field member of supannEntite)
### Actual behavior
![image](/uploads/31d07e7fb6b418351d5cfe2f253b0ea1/image.png)
No supannRefId is shown
### Expected behavior
Supann RefId should be available in this interface
dirty fix :
```
root@mc-pas-test:/usr/share/fusiondirectory/plugins/admin/supannStructures# diff class_etablissement.inc class_etablissement.inc.init
117,125d116
< new SetAttribute(
< new StringAttribute(
< _('Reference IDs'), _('supannRefId - IDs/links for this entity on other systems'),
< 'supannRefId', FALSE,
< '', '',
< // Validation regexp: it must have a prefix
< '/^{[^}]+}.+$/'
< )
< ),
```FusionDirectory 1.3.1Jonathan SwaelensJonathan Swaelenshttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/5905cannot add a password policy2019-03-22T13:54:05Zagallavardincannot add a password policy### Description
### Distribution Name and Version
debian Stretch
### FusionDirectory Version
1.4-dev ( maybe previous version)
### Plugin with the defect
ppolicy
### PHP version used
php5
### Origin of php packages
integrations ...### Description
### Distribution Name and Version
debian Stretch
### FusionDirectory Version
1.4-dev ( maybe previous version)
### Plugin with the defect
ppolicy
### PHP version used
php5
### Origin of php packages
integrations package
### Steps to Reproduce
1. add the default ppolicy
2. errors occurs :"pwdAttribute: value #0 invalid per syntax"
**Expected behavior:**
Password policie should be saved
**Actual behavior:**
errors occurs :"pwdAttribute: value #0 invalid per syntax"
policies not saved
**Reproduces how often:**
100 %
### Additional Information
Thanks to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717614
I have a work around :
change `new HiddenAttribute('pwdAttribute', TRUE, 'userPassword'),` to `new HiddenAttribute('pwdAttribute', TRUE, '2.5.4.35'),`
no Idea to resolve this bug
issues open for the other adminbmortierbmortierhttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/5900Next ID hook feature is broken2019-01-10T09:04:25ZagallavardinNext ID hook feature is broken### Description
an external script used for getting the next uid/gidnuimber could'nt be called
### Distribution Name and Version
Debian stretch
### FusionDirectory Version
1.3
### PHP version used
php7
### Origin of php packages
```...### Description
an external script used for getting the next uid/gidnuimber could'nt be called
### Distribution Name and Version
Debian stretch
### FusionDirectory Version
1.3
### PHP version used
php7
### Origin of php packages
```
root@mc-pas-qal:/home/spreaduser# dpkg -l fusiondirectory
Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
| État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements
|/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais)
||/ Nom Version Architecture Description
+++-===================================-======================-======================-============================================================================
ii fusiondirectory 1.3-2~jenkinsbuild64 all Web Based LDAP Administration Program
root@mc-pas-qal:/home/spreaduser#
```
### Steps to Reproduce
1. set a script or command that could be called by apache user in next id hook inside posix plugin
2. create an account with posix component ( not force uid gid) just set a primary group
3. click on ok
**Expected behavior:**
The script should be called by return the next id
```
root@mc-pas-qal:/home/spreaduser# su - www-data
$ /tmp/get-next-id.sh
1506
```
**Actual behavior:**
a non critic error occurs : `"«nextIdHook» n’est pas disponible. Utilisation de la base par défaut !"`
**Reproduces how often:**
100%
** additional information **
on : https://documentation.fusiondirectory.org/en/documentation/admin_installation/core_configuration
I see :
```
Next id hook: Defines a script to be called for finding the next free id for users or groups externally.
The script will receive concerned dn as first argument, and 'uid' or 'gid' as second argument, it should output a single number to use as uidNumber or gidNumber.
```
why dn is submit as argumentFusionDirectory 1.3Côme ChillietCôme Chilliethttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/5849fusiondirectory-plugin-renater-partage : gosaMailAlternateAddress domain suff...2018-08-09T11:37:30Zagallavardinfusiondirectory-plugin-renater-partage : gosaMailAlternateAddress domain suffix domain must be checked### Description
When using the partage plugin, all mail inside the gosaMailAlternateAddress must have the same domain mail as the domain mail specified in partage configuration.
this check must be done for group, sympaAlias and user gos...### Description
When using the partage plugin, all mail inside the gosaMailAlternateAddress must have the same domain mail as the domain mail specified in partage configuration.
this check must be done for group, sympaAlias and user gosaMailAlternateAddress
### Distribution Name and Version
Debian stretch
### FusionDirectory Version
fusiondirectory (1.3-2~jenkinsbuild37)
### Plugin with the defect
fusiondirectory-plugin-renater-partage-schema (1.3-2~jenkinsbuild37)
### PHP version used
php7.0
### Origin of php packages
Debian stretch packages
### Steps to Reproduce
1. create a sympAlias
2. add partage information
3. add partage alternate adress with an domain different diffrent from partage settings ( @free.fr instead of @irstea.fr)
**Expected behavior:**
A error message should occurs like : :
an alternate e-mail address didn't correspond to the domain name specified on mail serveur ( allowed value : (server domain name here!))
**Actual behavior:**
Error 500 when partage plugin try to add the alternate adress
**Reproduces how often:**
100%FusionDirectory 1.3Côme ChillietCôme Chilliethttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/5848Matching mail suffix between PARTAGE and FD2018-08-08T12:27:39ZagallavardinMatching mail suffix between PARTAGE and FD### Description
When adding or modifying, partage information related to Sympa Alias, it doesn't work because PARTAGE receive a non-valid request
### Distribution Name and Version
Debian Stretch
### FusionDirectory Version
`ii fusio...### Description
When adding or modifying, partage information related to Sympa Alias, it doesn't work because PARTAGE receive a non-valid request
### Distribution Name and Version
Debian Stretch
### FusionDirectory Version
`ii fusiondirectory 1.3-2~jenkinsbuild28 all Web Based LDAP Administration Program`
### Plugin with the defect
```
ii fusiondirectory-plugin-renater-partage 1.3-2~jenkinsbuild28 all Renater partage integration plugin for FusionDirectory
ii fusiondirectory-plugin-renater-partage-schema 1.3-2~jenkinsbuild28 all LDAP schema for FusionDirectory renater partage plugin
```
### PHP version used
`ii php7.0 7.0.30-0+deb9u1 all server-side,`
### Origin of php packages
From deb :
```
php7.0:
Installé : 7.0.30-0+deb9u1
Candidat : 7.0.30-0+deb9u1
Table de version :
*** 7.0.30-0+deb9u1 500
500 http://ftp.fr.debian.org/debian stretch/main amd64 Packages
500 http://security.debian.org/debian-security stretch/updates/main amd64 Packages
100 /var/lib/dpkg/status
```
### Steps to Reproduce
1. add a sympa alias list without partage information
2. Add partage information
3. Wait the error
**Expected behavior:**
Partage information must be created / updated on Partage Infra
**Actual behavior:**
Error :
on browser
`Impossible de mettre à jour le compte : Impossible de se connecter à https://api.partage.renater.fr/service/domain/: fopen(https://api.partage.renater.fr/service/domain//CreateGroup/22f97c76cf9a11405cdb5e740fc0aad3): failed to open stream: HTTP request failed! HTTP/1.1 403 Forbidden `
with debug :
```
DEBUG[512] (/usr/share/fusiondirectory/plugins/personal/mail/mail-methods/class_mail-methods-renater-partage.inc:query():85) - MAIL: Command: 'CreateGroup'
DEBUG[512] (/usr/share/fusiondirectory/plugins/personal/mail/mail-methods/class_mail-methods-renater-partage.inc:query():86) - MAIL: Query: 'name=fakelist%40lists.irstea.fr&description=liste+de+fake&displayName=FAKE+LIST&zimbraMailStatus=enabled&zimbraHideInGal=TRUE&zimbraDistributionListSendShareMessageToNewMembers=FALSE'
DEBUG[512] (/usr/share/fusiondirectory/plugins/personal/mail/mail-methods/class_mail-methods-renater-partage.inc:query():142) - MAIL: No Answer:
```
**Reproduces how often:**
100%
### Additional Information
Basically :
* our partage domain is : company.fr ( all created object as user, group .. MUST have the mail suffix @company.fr
* our Sympa domain list is : lists.company.fr
We want to have an alias for 2 reasons
* appearing lists in global catalogue of PARTAGE
* have an alias mylist@company.fr to mylist@lists.company.fr
so the group created on PARTAGE side MUST have the suffix @company.fr and a forwarding address to mylist@lists.company.fr
On debug we see :
MAIL: Query: 'name=fakelist%40lists.irstea.fr&descri ....
`'name=fakelist%40lists.irstea.fr isn"t correct !! It must be name=fakelist%40irstea.fr`
the mail domain must be taken from the PARTAGE COS used.
After creation of this group a new request is needed to add as member of fakelist%40irstea.fr the adress contain in CN field : fakelist%40lists.irstea.frFusionDirectory 1.3Côme ChillietCôme Chilliethttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/5807domain mail add twice when edit the RENATER partage parameters2018-08-08T10:24:56Zagallavardindomain mail add twice when edit the RENATER partage parameters### Description
In Renater Partage plugin associated to sympa plugin , When a entry is edited I gopt an ERROR 500 when FD trying to make modification trough the web service
![err1](/uploads/0e8317e4a4f875ccf96a38f85c03ed7f/err1.png)
##...### Description
In Renater Partage plugin associated to sympa plugin , When a entry is edited I gopt an ERROR 500 when FD trying to make modification trough the web service
![err1](/uploads/0e8317e4a4f875ccf96a38f85c03ed7f/err1.png)
### Distribution Name and Version
on debian stretch
### FusionDirectory Version
```
ii fusiondirectory-plugin-renater-partage 1.2-2~jenkinsbuild799 all Renater partage integration plugin for FusionDirectory
ii fusiondirectory-plugin-renater-partage-schema 1.2-2~jenkinsbuild799 all LDAP schema for FusionDirectory renater partage plugin
```
### Plugin with the defect
plugin-renater-partage
### PHP version used
<!-- Required -->
### Origin of php packages
```
apt-cache policy php
php:
Installé : 1:7.0+49
Candidat : 1:7.0+49
Table de version :
*** 1:7.0+49 500
500 http://ftp.fr.debian.org/debian stretch/main amd64 Packages
100 /var/lib/dpkg/status
```
### Steps to Reproduce
I Try to add Partage information applied to a list
**Expected behavior:**
PD should create or modified a group on Partage side
**Actual behavior:**
Error when trying top make some modification due to a incorrect partage account , FD add Partage domain name even if "cn" field contain a domain name
![err2](/uploads/ac4ff16fa390c1167567543ad333d446/err2.png)
It's a side effect of #5804FusionDirectory 1.3Côme ChillietCôme Chilliethttps://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/issues/5776Openldap Project update ppolicy schema2020-04-22T12:23:56ZagallavardinOpenldap Project update ppolicy schemaWhen we upgrade slapd on Debian stretch, slapd-ppolicy is upgraded
Internal schema of ppolicy is upgraded too
see : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815364#38
schema provided by debian package is put as attachment
> ii...When we upgrade slapd on Debian stretch, slapd-ppolicy is upgraded
Internal schema of ppolicy is upgraded too
see : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815364#38
schema provided by debian package is put as attachment
> ii slapd 2.4.44+dfsg-5+deb9u1
[ppolicy.schema](/uploads/baf794af666805583e1d3f771383ecfc/ppolicy.schema)
maybe doc and code should be adaptedFusionDirectory 1.4Côme ChillietCôme Chilliet