[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kolab-users
Subject:    Re: ldap Extensions
From:       Jean-Michel Dault <jmdault () mandrakesoft ! com>
Date:       2004-10-08 2:37:06
Message-ID: 1097203026.3357.19.camel () jmlap ! mandrakesoft ! com
[Download RAW message or body]

Le jeu 07/10/2004 à 11:44, Martin Konold a écrit :
> Am Donnerstag, 7. Oktober 2004 15:39 schrieb Jean-Michel Dault:
> Hi JM,
> > To solve the problem, I read the original entry, then store it in an
> > array "orig_object". 
> How is this supposed to work with write only (no read access) passwords?

Hmm.. I don't quite understand your point, as in Kolab 1.0, the user has
access to his password, and manager has access to it too. This stuff
might have changed in 2.0, I haven't had the time to look at the code.

But as far as I know, Kolab 1.0 cannot deal with write only passwords,
because of the way it handles a change in First and Last Name: it does a
ldap_add on the new dn and then a ldap_delete. So if the password cannot
be read, the new ldap entry wouldn't have any password.

-- 
Jean-Michel Dault <jmdault@mandrakesoft.com>


[prev in list] [next in list] [prev in thread] [next in thread]