[Phpgroupware-tracker] [bug #14827] Modification of a user within PHPGW that is created with smbldap-tools kills LDAP entry

[Caeies]

Follow-up Comment #8, bug #14827 (project phpgroupware):

Hi Marco,

That's look better, and will help you to understand how difficult it is for
us to work out this properly.

I don't know what's your skills in LDAP, but here's the problem :

In your case, you use the "person" objectclass to classify people, this is a
"structural class" which means the "base".

In the case of phpgw the choice was done to use the "Account" objectclass as
the "base" or "structural class".

As you can guess, having two structural classes is not an option, and ldap
complains about objectclass violation.

The only simple solution I found, is that the admin user indicates what's the
"structural class" is in his case ... so we should avoid the problem you get.
We can't do this automatically because we have no convenient way to guess
what's the structural class used ...

Now, answering to others remarks :
no data altered : of course, LDAP complains, so no modifcation are able to be
done.
contacts added : that's still a consequence of the not being able to modify
the classes ... because the contact_id is never stored and so phpgw decide to
create a new one because for it it doesn't exist.

Last state :
No :) It's already the case ... this will not solve most problems which are
in your case very specific.

Hope that clear,

A patch will follow in a few minutes.

Regards,

Caeies

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?func=detailitem&item_id=14827>

_______________________________________________
  Message posté via/par Savannah
  http://savannah.gnu.org/