#1071096 gosa: default ldap setup requires schema whose installation is apparently non-trivial to figure out and broken

Package:
gosa
Source:
gosa
Submitter:
Josip Rodin
Date:
2025-03-27 12:27:01 UTC
Severity:
normal
#1071096#5
Date:
2024-05-14 08:40:17 UTC
From:
To:
Hi,

So I wanted something to replace phpldapadmin, this turned up in apt cache
search web ldap, and so I installed it, opened the /gosa URL on the website,
authorized it with the provided shell command, connected to the pre-existing
slapd, and then /gosa/setup.php said:

  LDAP schema check
  5 / 7
  Schema specific settings
  warning
  Attention
  Schema check failed The following object classes are missing:

      gosaObject
      gosaAccount
      gosaLockEntry
      gosaDepartment
      gosaCacheEntry
      gosaProperties
      gosaConfig

If this is not optional, it needs to be stated somewhere more prominently,
or it needs to be made optional. The package description says "Web Based
LDAP Administration Program", it does not say it only works with its own
LDAP schema.

/usr/share/doc/gosa/README.Debian says at the very bottom:

This is apparently untrue. It would be better not to make such sweeping
statements at the start of the documentation.

Installed the package, it does not ship any such directory:

% dpkg -L gosa-schema | grep /usr/share/doc/gosa/contrib/openldap
%
couple of Debian releases, so this is useless as is?

I noticed the same .schema files are accompanied by .ldif files, which could
be usable. However, trying that produced:

% sudo ldapadd -Y EXTERNAL -H ldapi:/// -f /etc/ldap/schema/gosa/gosa-samba3.ldif
SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
ldapadd: invalid format (line 57) entry: "cn=gosa-samba3,cn=schema,cn=config"

So, yeah, all in all this is a very frustrating onboarding experience.

Please fix it. TIA.
#1071096#10
Date:
2025-03-27 12:25:06 UTC
From:
To:
I had the same issue when trying to migrate from fusion directory. I
thought it was because I had fusion directory schema already present, so
I opened https://github.com/gosa-project/gosa-core/issues/66 for
migration documentation.

But figured out even a fresh slapd installation does not work. Though it
failed much earlier in the setup, it does not proceed after the LDAP
server configuration screen. Clicking on Continue button keeps
refreshing the screen, the connection is shown as successful.

Note: the default screen is in German and I had to use LibreWolf/Firefox
translate to try it.