[Phpgroupware-tracker] [patch #3333] ENH: LDAP Better error messaging/handling

[Greg Valcourt]

This mail is an automated notification from the patch tracker
 of the project: phpGroupWare.

/**************************************************************************/
[patch #3333] Latest Modifications:

Changes by: 
                Greg Valcourt <address@hidden>
'Date: 
                Fri 10/01/04 at 19:07 (GMT)

------------------ Additional Follow-up Comments ----------------------------
I agree. I submitted that patch a bit hastily. I have come up with a solution 
for the mean time: create a seperate branch in LDAP for groupware groups. 






/**************************************************************************/
[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 16: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: Fri 10/01/04 at 19:07         By: Greg Valcourt <gval>
I agree. I submitted that patch a bit hastily. I have come up with a solution 
for the mean time: create a seperate branch in LDAP for groupware groups. 

-------------------------------------------------------
Date: Wed 09/29/04 at 06:53         By: Caeies <Caeies>
Unfortunately, the SQL code is not compatible with this kind of thing.
We need to rewrite the SQL way of handling groups and accounts in SQL to be 
able to change them in account_ldap
This could be a problem for example, when trying to switch from LDAP to SQL 
like authentification.

Regards,

Caeies.

-------------------------------------------------------
Date: Wed 09/01/04 at 18: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 16:58  Name: patchfile.diff  Size: 2.84KB   By: None

http://savannah.gnu.org/patch/download.php?item_id=3333&amp;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/