[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Phpgroupware-tracker] [patch #3333] ENH: LDAP Better error messaging/ha
From: |
anonymous |
Subject: |
[Phpgroupware-tracker] [patch #3333] ENH: LDAP Better error messaging/handling |
Date: |
Wed, 01 Sep 2004 14:06:06 -0400 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040413 Debian/1.6-5 |
This mail is an automated notification from the patch tracker
of the project: phpGroupWare.
/**************************************************************************/
[patch #3333] Latest Modifications:
Changes by: Anonymous user
Date:
Wed 09/01/04 at 14:01
------------------ Additional Follow-up Comments ----------------------------
Target Branch: 0.9.16, HEAD
Purpose: More thorough error messages in ldapmodify, account/group id number
conflict should not be a fatal error.
Format: diff
Affected file/s: setup/ldapmodify.php, phpgwapi/inc/class.accounts_ldap.inc.php
ldapmodify now prints dn used, and what the error returned from the
ldap_mod_replace function was when adding a user already in ldap.
The login page was giving a fatal error when you tried to login and you had an
uid number that was the same as a gid in ldap. uid's and gid's are not related
and you will usually find many uid's that are the same number as a gid. I
changed the get_type() function to return type as 'u' when both numbers exist.
If this is a problem, perhaps consider having collissions generate warnings.
/**************************************************************************/
[patch #3333] Full Item Snapshot:
URL: <http://savannah.gnu.org/patch/?func=detailitem&item_id=3333>
Project: phpGroupWare
Submitted by: 0
On: Wed 09/01/04 at 12:58
Category: None
Priority: 5 - Normal
Resolution: None
Privacy: Public
Assigned to: None
Originator Email: address@hidden
Status: Open
Summary: ENH: LDAP Better error messaging/handling
Original Submission:
Follow-up Comments
------------------
-------------------------------------------------------
Date: Wed 09/01/04 at 14:01 By: 0 <None>
Target Branch: 0.9.16, HEAD
Purpose: More thorough error messages in ldapmodify, account/group id number
conflict should not be a fatal error.
Format: diff
Affected file/s: setup/ldapmodify.php, phpgwapi/inc/class.accounts_ldap.inc.php
ldapmodify now prints dn used, and what the error returned from the
ldap_mod_replace function was when adding a user already in ldap.
The login page was giving a fatal error when you tried to login and you had an
uid number that was the same as a gid in ldap. uid's and gid's are not related
and you will usually find many uid's that are the same number as a gid. I
changed the get_type() function to return type as 'u' when both numbers exist.
If this is a problem, perhaps consider having collissions generate warnings.
File Attachments
-------------------
-------------------------------------------------------
Date: Wed 09/01/04 at 12:58 Name: patchfile.diff Size: 2.84KB By: None
http://savannah.gnu.org/patch/download.php?item_id=3333&item_file_id=3629
For detailed info, follow this link:
<http://savannah.gnu.org/patch/?func=detailitem&item_id=3333>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/