Next 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

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 argument

assigned to @MCMic

changed the description

changed the description

changed milestone to %FusionDirectory 1.3

added fd628 fd760 fd396 fd464 labels

added fd~380 label

created branch 5936-unable-to-use-nexthook-id

created branch 5900-unable-to-use-nexthook-id

mentioned in commit 69b74b70

why dn is submit as argument

@gallak So that the script can test if the user is a new one or existing one and may fetch info from LDAP if it’s an existing one.

Also, please note that the first argument is the name of the LDAP field concerned, so either uidNumber or gidNumber (and not just uid or gid).

added user-manual label

created branch 5900-unable-to-use-nexthook-id

mentioned in commit 5f71b76e