[Kroupware] Web interface frontend

[Tassilo Erlewein]

Am Sonntag, 29. September 2002 16:20 schrieb konold@erfrakon.de:

> > no business card contains a userpassword to my knowledge.
> >
> > an object might be both: a contact/person/... and an account
> > (or an whatwasthenameoftheitemthatallowestohaveauserpassword),
> > but a contact per se has no userpassword.
>
> Tassilo: Do you want to comment on this?

About the LDAP stuff - let me clearify that point a little bit:

for authentication purposes (Cyrus IMAP and Postfix via saslauthd with=20
experimental ldap enabled, Apache2 with experimental mod_auth_ldap) one n=
eeds=20
the ldap object referring to a user to have exactly this two attributes:
1. uid (easily configurable)
2. userPassword
The layout of the tree or even the rest of the user object attributes don=
't=20
matter with regard to authentication.

So, the user object layout is mainly determined by the requirements of th=
e=20
global shared address book _and_ the compatibility to vcard (import/expor=
t to=20
personal contacts which are not stored within ldap at this time).
=20
And yes you're right this should be discussed.  We can discuss whether=20
inetOrgPerson is good enough, or how we extend it, etc. etc. etc.
Tobias has made an interesting suggestion in another mail; this could be =
a=20
good direction to go :-) I like to hear contributions about this.

We just have to find a very flexible admin web interface frontend then an=
d=20
still be somewhat understandable by the folks who happen to not be ldap=20
addicts and don't wish to become it.

For outlook (tm) compatibility however we should not end up too far from=20
inetOrgPerson, I afraid.

Tassilo