Egw ldap schema compatible with courier-ldap?

alberto_pm 2007-02-19 20:28:26 UTC #1

Hi folks,

i have setup egw with user accounts and addressbook on openldap.
Now i am trying to setup an imap mail server. I have seen courier-ldap has it’s own ldap schema for the accounts.

Is there a way that i use the same schema for both egw and courier? I want to setup ONE single account for each user, so that they can access egw and mail.

Has anybody experiences in that matter?
Any help or suggestion appreciated.

Thanks.
Alberto.

Lars_Kneschke-2 2007-02-21 18:21:19 UTC #2

“alberto_pm” alberto.perdomo@gmail.com schrieb:

Hi folks,

i have setup egw with user accounts and addressbook on openldap.
Now i am trying to setup an imap mail server. I have seen courier-ldap
has
it’s own ldap schema for the accounts.

Is there a way that i use the same schema for both egw and courier? I
want
to setup ONE single account for each user, so that they can access egw
and
mail.

Has anybody experiences in that matter?
Any help or suggestion appreciated.

Can you tell me a little bit more about the courier ldap schema?

–
Lars Kneschke
Metaways Infosystems GmbH
Pickhuben 2-4, D-20457
Hamburg

eGroupWare Training & Support ==>
http://www.egroupware-support.net

E-Mail:
mailto:l.kneschke@metaways.de
Web: http://www.metaways.de
Tel: +49 (0)40
317031-21
Fax: +49 (0)40 317031-81
Mobile: +49 (0)175 9304324

Metaways
Infosystems GmbH - Sitz: D-22967 Tremsbüttel
Handelsregister: Amtsgericht
Ahrensburg HRB 4508
Geschäftsführung: Hermann Thaele, Lüder-H.Thaele

Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net’s Techsay panel and you’ll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

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

alberto_pm 2007-02-21 19:53:38 UTC #3

Hi.

Well, in order to store the addressbook contacts in LDAP and to validate the users with LDAP i have setup openldap to include the schemas for EGW:

include /usr/share/egroupware-ldap/phpgwaccount.schema
include /usr/share/egroupware-ldap/phpgwcontact.schema

OK, so i got addressbook contacts and accounts stored in LDAP.
My next step is i want to setup an IMAP server. Because i don’t want to handle separate accounts for each service (mail, egw, subversion, etc.) i want to validate all this services against the LDAP server.

The schema for courier-ldap is /usr/share/doc/courier-ldap/authldap.schema which has other objectClasses like “couriermailaccount”. You can see the file on http://www.tom.sfc.keio.ac.jp/~torry/ldap/data/authldap.schema. An example of an LDAP account for courier looks the following:

dn: cn=Name Surname,ou=People, o=domain,c=com
cn: Name Surname
gidNumber: 5000
mail: login@domain.com
sn: surname
uidNumber: 5000
objectClass: couriermailaccount
objectClass: person
objectClass: top
objectClass: inetOrgPerson
homeDirectory: /var/vmail
quota: 0
mailbox: domain.com/login/
userPassword: {CRYPT}password

So i gues if i want LDAP accounts to work for egw and courier i have to also include the schema for courier and then create the accounts with ldapadd instead of with egw. The created account should have all the objects and properties required both by egw and courier.

I have also customized the addressbook by adding a few extra fields and i was shocked to see that they are not stored in LDAP. Does this mean that customized fields are stored in the database backend and the “regular” fields are stored in LDAP?

Hope i explained my self clearly enough. If not just tell me.

Thanks for your help.

Regards.

"alberto_pm" schrieb: > > Hi folks, > > i have setup egw with user accounts and addressbook on openldap. > Now i am trying to setup an imap mail server. I have seen courier-ldap has > it's own ldap schema for the accounts. > > Is there a way that i use the same schema for both egw and courier? I want > to setup ONE single account for each user, so that they can access egw and > mail. > > Has anybody experiences in that matter? > Any help or suggestion appreciated.

Can you tell me a little bit more about the courier ldap schema?

–
Lars Kneschke
Metaways Infosystems GmbH
Pickhuben 2-4, D-20457
Hamburg

eGroupWare Training & Support ==>
http://www.egroupware-support.net

E-Mail:
mailto:l.kneschke@metaways.de
Web: http://www.metaways.de
Tel: +49 (0)40
317031-21
Fax: +49 (0)40 317031-81
Mobile: +49 (0)175 9304324

Metaways
Infosystems GmbH - Sitz: D-22967 Tremsbüttel
Handelsregister: Amtsgericht
Ahrensburg HRB 4508
Geschäftsführung: Hermann Thaele, Lüder-H.Thaele

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

[/quote]

Lars_Kneschke-2 2007-02-21 20:44:52 UTC #4

“alberto_pm” alberto.perdomo@gmail.com schrieb:

The schema for courier-ldap is
/usr/share/doc/courier-ldap/authldap.schema
which has other objectClasses like “couriermailaccount”. You can see the
file on http://www.tom.sfc.keio.ac.jp/~torry/ldap/data/authldap.schema.
An
example of an LDAP account for courier looks the following:

dn: cn=Name Surname,ou=People, o=domain,c=com
cn: Name Surname
gidNumber: 5000
mail: login@domain.com
sn: surname
uidNumber: 5000
objectClass: couriermailaccount
objectClass: person
objectClass: top
objectClass: inetOrgPerson
homeDirectory: /var/vmail
quota: 0
mailbox: domain.com/login/
userPassword: {CRYPT}password
We can extend emailadmin easily to handle the needed ldap fields for
courier too. Can you give me access to this system?

I have also customized the addressbook by adding a few extra fields and i
was shocked to see that they are not stored in LDAP. Does this mean that
customized fields are stored in the database backend and the "regular"
fields are stored in LDAP?
Yes. No other client can read the customized fields. It’s our philosophy to
store only that fields in LDAP which also be read by other ldap clients and
to use existing ldap schemas if possible.

–
Lars Kneschke
Metaways Infosystems GmbH
Pickhuben 2-4, D-20457
Hamburg

eGroupWare Training & Support ==>
http://www.egroupware-support.net

E-Mail:
mailto:l.kneschke@metaways.de
Web: http://www.metaways.de
Tel: +49 (0)40
317031-21
Fax: +49 (0)40 317031-81
Mobile: +49 (0)175 9304324

Metaways
Infosystems GmbH - Sitz: D-22967 Tremsbüttel
Handelsregister: Amtsgericht
Ahrensburg HRB 4508
Geschäftsführung: Hermann Thaele, Lüder-H.Thaele

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

alberto_pm 2007-02-21 21:18:43 UTC #5

Hi Lars,

i have looked at email admin and it look like pretty basic configuration, isn’t it?
I didn’t see any LDAP related fields at all there.

What do you mean by “extend”? A patch or so?
I am looking for a long-term solution since i want to add more ldap-validated-services within the next days/weeks (e.g. subversion, jabber, etc.). So the email configuration is just the first of them i have to deal with. Next thing i will have to deal wtih will be PAM and NSS (in order for subversion to work with LDAP).

So can i maybe include those “other” ldap schemas within the LDAP server configuration and then create the accounts directly on the LDAP server instead of in EGW? I could write myself a template of new users containing all needed values by egw, subversion, mail, jabber, etc.

What kind of access do you mean? SSH? Or an admin login to the EGW application? Access to the mail machine? the LDAP machine? or the EGW machine?

Thanks.

Regards,
Alberto.

"alberto_pm" schrieb: > > The schema for courier-ldap is /usr/share/doc/courier-ldap/authldap.schema > which has other objectClasses like "couriermailaccount". You can see the > file on http://www.tom.sfc.keio.ac.jp/~torry/ldap/data/authldap.schema. An > example of an LDAP account for courier looks the following: > > dn: cn=Name Surname,ou=People, o=domain,c=com > cn: Name Surname > gidNumber: 5000 > mail: login@domain.com > sn: surname > uidNumber: 5000 > objectClass: couriermailaccount > objectClass: person > objectClass: top > objectClass: inetOrgPerson > homeDirectory: /var/vmail > quota: 0 > mailbox: domain.com/login/ > userPassword: {CRYPT}password We can extend emailadmin easily to handle the needed ldap fields for courier too. Can you give me access to this system?

I have also customized the addressbook by adding a few extra fields and i
was shocked to see that they are not stored in LDAP. Does this mean that
customized fields are stored in the database backend and the "regular"
fields are stored in LDAP?
Yes. No other client can read the customized fields. It’s our philosophy to
store only that fields in LDAP which also be read by other ldap clients and
to use existing ldap schemas if possible.

–
Lars Kneschke
Metaways Infosystems GmbH
Pickhuben 2-4, D-20457
Hamburg

eGroupWare Training & Support ==>
http://www.egroupware-support.net

E-Mail:
mailto:l.kneschke@metaways.de
Web: http://www.metaways.de
Tel: +49 (0)40
317031-21
Fax: +49 (0)40 317031-81
Mobile: +49 (0)175 9304324

Metaways
Infosystems GmbH - Sitz: D-22967 Tremsbüttel
Handelsregister: Amtsgericht
Ahrensburg HRB 4508
Geschäftsführung: Hermann Thaele, Lüder-H.Thaele

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

[/quote]