Hi,
I've found an old post in the list archives regarding the integration of eGroupWare with FDS, and some posts in the eGroupWare forums. Unfortunately, none of the discussions lead to a solution.
References : http://www.redhat.com/archives/fedora-directory-users/2005-July/msg00199.htm... http://forum.egroupware.org/viewtopic.php?t=3257 http://forum.egroupware.org/viewtopic.php?t=7456
I'm having the same problem : The schema files provided with eGroupWare don't work as-is with FDS, it's not just a matter of renaming them to "NNfilename.ldif". Files for OpenLDAP, iPlanet (unfortunately quite different, they don't even have any "dn: cn=schema" lines) and Novell eDirectory (the closest match is seems, but still different and marked as EXPERIMENTAL) can all be found here :
http://svn.egroupware.org/egroupware/trunk/phpgwapi/doc/ldap/
The README contains all the details.
So... the same question : Has anyone created FDS LDIF files based on these, to drop in the config/schemas/ directory and have eGroupWare working? :-)
Matthias
Hi,
Replying to myself and attaching some LDIF files I've made based on the ones provided for the Novell server. It seems to work, although I have two doubts :
- The phpgwContactOwner had : 1.3.6.1.4.1.1466.115.121.1.36{16} which couldn't be found, so I changed it to : 1.3.6.1.4.1.1466.115.121.1.15{16} like all the other similar attributes
- The phpgwAudio had : 1.3.6.1.4.1.1466.115.121.1.4{25000} which couldn't be found either, so I changed it to : SUP name which I know is wrong since other schemas have "bin" here
Does anyone know for sure if the LDIFs I've made are correct? If the first change makes sense and what the proper change for the second would be?
I didn't bother much about those two issues since they seem to only apply for contacts, and the phpgwAudio is something I'll probably never use. eGroupWare is working currently, which is a good step forward already!
Matthias
Matthias Saou wrote:
Hi,
Replying to myself and attaching some LDIF files I've made based on the ones provided for the Novell server. It seems to work, although I have two doubts :
- The phpgwContactOwner had : 1.3.6.1.4.1.1466.115.121.1.36{16} which couldn't be found, so I changed it to : 1.3.6.1.4.1.1466.115.121.1.15{16} like all the other similar attributes
That's numeric string - that's fine.
- The phpgwAudio had : 1.3.6.1.4.1.1466.115.121.1.4{25000} which couldn't be found either, so I changed it to : SUP name which I know is wrong since other schemas have "bin" here
I would change the syntax from audio to binary - likelyhood is your applications won't care.
1.3.6.1.4.1.1466.115.121.1.5
Does anyone know for sure if the LDIFs I've made are correct? If the first change makes sense and what the proper change for the second would be?
I didn't bother much about those two issues since they seem to only apply for contacts, and the phpgwAudio is something I'll probably never use. eGroupWare is working currently, which is a good step forward already!
Matthias
-- Fedora-directory-users mailing list Fedora-directory-users@redhat.com https://www.redhat.com/mailman/listinfo/fedora-directory-users
Pete Rowley wrote :
Replying to myself and attaching some LDIF files I've made based on the ones provided for the Novell server. It seems to work, although I have two doubts :
- The phpgwContactOwner had : 1.3.6.1.4.1.1466.115.121.1.36{16} which couldn't be found, so I changed it to : 1.3.6.1.4.1.1466.115.121.1.15{16} like all the other similar attributes
That's numeric string - that's fine.
- The phpgwAudio had : 1.3.6.1.4.1.1466.115.121.1.4{25000} which couldn't be found either, so I changed it to : SUP name which I know is wrong since other schemas have "bin" here
I would change the syntax from audio to binary - likelyhood is your applications won't care.
1.3.6.1.4.1.1466.115.121.1.5
Thanks a lot for the clarifications. I'll be forwarding these LDIFs to the eGroupWare forums since this seems to be a FAQ.
Matthias
389-users@lists.fedoraproject.org