[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Phpgroupware-tracker] [bug #14827] Modification of a user within PHPGW
From: |
Caeies |
Subject: |
[Phpgroupware-tracker] [bug #14827] Modification of a user within PHPGW that is created with smbldap-tools kills LDAP entry |
Date: |
Wed, 26 Oct 2005 08:08:14 +0000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050925 Firefox/1.0.4 (Debian package 1.0.4-2sarge5) |
Follow-up Comment #3, bug #14827 (project phpgroupware):
Hi all,
Finally get some time to look at this.
Well, If a user is auto added, the first result is "ok", when looking at the
code (I mean the new test user). Why ?
In fact, the auto_add function consider that the user doesn't exist in the
ldap system ... he is just authenticated through ldap, and his account is
"created". But the function responsible for the creation of an account find
the old entry and replace it with new values ... So in some way this is the
normal behavior (at least the documented one :)
Is this good or wrong ... well that's open discussion.
Then, about the admin failing to save values ... there is clearly a problem
since the objectclass is missing
objectClass: inetOrgPerson
objectClass: shadowAccount
objectClass: sambaSamAccount
objectClass: inetLocalMailRecipient
But still gets its entries ...
So remaining question is why the create_account is ok in the auto_add
function and deficient in the admin case ?
I'm investigating this now.
Anyway, Could you please check that your config is using the right values for
group account and user account (min / max)
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=14827>
_______________________________________________
Message posté via/par Savannah
http://savannah.gnu.org/