difference in provided ldap server in debian and Centos
Hello,
the root object in the ldap tree is different in Debian and Centos. On Debian the root object and admin is made by the package and we got this on the root object who is right :
0 dc=labo,dc=opensides,dc=be o: OpenSides dc: labo ou: labo description: labo objectClass: top objectClass: dcObject objectClass: organization objectClass: gosaDepartment objectClass: gosaAcl gosaAclEntry: 0:subtree:Y249YWRtaW4sb3U9YWNscm9sZXMsZGM9bGFibyxkYz1vcGVuc2lkZXMsZGM9YmU=:dWlkPWZkLWFkbWluLG91PXBlb3BsZSxkYz1sYWJvLGRjPW9wZW5zaWRlcyxkYz1iZQ==
The one made by the FusionDirectory setup is looking like this
0 dc=inalco,dc=fr dc: inalco ou: inalco description: inalco objectClass: top objectClass: dcObject objectClass: locality objectClass: gosaDepartment objectClass: gosaAcl gosaAclEntry: 0:subtree:Y249YWRtaW4sb3U9YWNscm9sZXMsZGM9aW5hbGNvLGRjPWZy:dWlkPWZkLWFkbWluLG91PXBlb3BsZSxkYz1pbmFsY28sZGM9ZnI=
as you can see the locality objectClass is put there in place of the organization objectClass and this cree a conflict with the root attributes and objectClass of the Supann architecture
Cheers
(from redmine: issue id 4231, created on 2015-10-20, closed on 2015-10-20)
- Changesets:
- Revision eb39b864 by Côme Chilliet on 2015-10-20T08:48:30.000Z:
Fixes #4231 Fixing the way dcObject are built- Revision 38df94fe by Côme Chilliet on 2015-10-20T08:49:07.000Z:
Fixes #4231 Fixing the way dcObject are built- Custom Fields:
- Bug in version: 1.0.9.1