LDAP scheme requirements

[Bugzilla_from_hadmut]

Hi,

I just tried to use egroupware with an existing LDAP infrastructure, but it did not find any user.

The reason is that the filter

(phpgwaccounttype=u)

is hardcoded and thus egroupware strictly requires proprietary schema extensions and rebuilding the LDAP objects.

This is a strict reason for not using egroupware here.

What exactly is the reason that egroupware would not work with plain standard LDAP accounts?

regards

[Ralf_Becker_6]

This is an only eGW Version, the current one 1.4 does NOT use the
phpgwaccount schema any more, but posixAccount and shadowAccount.
Requirement for an account is the check for posixAccount.

Ralf

Hadmut schrieb:

Hi,

I just tried to use egroupware with an existing LDAP infrastructure, but it
did not find any user.

The reason is that the filter

(phpgwaccounttype=u)

is hardcoded and thus egroupware strictly requires proprietary schema
extensions and rebuilding the LDAP objects.

This is a strict reason for not using egroupware here.

What exactly is the reason that egroupware would not work with plain
standard LDAP accounts?

regards

–
Ralf Becker
eGroupWare Training & Support ==> http://www.egroupware-support.de
Outdoor Unlimited Training GmbH [www.outdoor-training.de]
Handelsregister HRB Kaiserslautern 3587
Geschäftsführer Birgit und Ralf Becker
Leibnizstr. 17, 67663 Kaiserslautern, Germany
Telefon +49 (0)631 31657-0

---

This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don’t miss this year’s exciting event. There’s still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

---

eGroupWare-developers mailing list
eGroupWare-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-developers