Skip to content

[Bug]: posixGroup gidNumber cannot be 0 #484

Description

@calculoso

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
  1. Using the gui, try to re-save this same entry (click on cn=Administrator, click on Edit button, Click on Update)
  2. Observe that the "The gidnumber.null.0 field must be at least 1." error appears
Image

Relevant log output

Anything else?

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions