[Bug]: posixGroup gidNumber cannot be 0 #484

Is there an existing issue for this?

• I have searched the existing issues

Environment

- image: phpldapadmin/phpldapadmin:latest container
- LDAP Server: image: vegardit/openldap:latest container

- also validated on https://demo.phpldapadmin.org/

PLA Code

Docker hub

PLA Version

docker phpldapadmin/phpldapadmin:latest (8f17a6415432)

Current Behavior

Creating a posixGroup with a gidNumber of 0. phpLDAPadmin rejects the value of 0, saying a minimum value of 1 is required.

Expected Behavior

Expect that posix gidNumber of 0 is allowed.

Steps To Reproduce

1. on https://demo.phpldapadmin.org/ go to the dc=example,dc=com entry.
2. Import this ldif, to show that the gidNumber value is allowed

version: 1
dn: cn=Administrator,dc=example,dc=com
cn: Administrator
gidNumber: 0
objectClass: posixGroup

3. Using the gui, try to re-save this same entry (click on cn=Administrator, click on Edit button, Click on Update)
4. Observe that the "The gidnumber.null.0 field must be at least 1." error appears

Relevant log output

Anything else?

I used image: ldapaccountmanager/lam:latest and it allowed the gidNumber of 0 to be set.