#27576 [Opn]: Race condition inherent in php_ldap
| From: | derick@php.net | Date: | Fri, 12 Mar 2004 08:28:32 +0000 |
| Subject: | #27576 [Opn]: Race condition inherent in php_ldap | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-56351@lists.php.net to get a copy of this message | ||
ID: 27576
Updated by: derick@php.net
Reported By: jcllings at javahop dot com
Status: Open
-Bug Type: LDAP related
+Bug Type: Feature/Change Request
Operating System: Probably ALL
PHP Version: 4.3.5RC3
New Comment:
This is not really a bug, but more a feature request. Reclassifying.
Previous Comments:
------------------------------------------------------------------------
[2004-03-11 20:09:13] jcllings at javahop dot com
Description:
------------
From the documentation:
ldap_modify() function is used to modify the existing entries in the
LDAP directory. The structure of the entry is same as in ldap_add().
...and
bool ldap_add ( resource link_identifier, string dn, array entry)
The replace also has the same prototype:
bool ldap_mod_replace ( resource link_identifier, string dn, array
entry)
Where, according to the doc, 'resource link_identifier' is the
connection, 'string dn' is who to bind as and 'array entry' is the
modified data. No ability to specify *what* to modify so we will have
to perform a separate action to retrieve this. In the meantime the
data has been changed by another process, perhaps.
Allow me to further illustrate:
If Jon's email address is the old one, update it to the new one. This
activity cannot be safely performed because using PHP you have to
implement it in a two step process creating a potential race
condition.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=27576&edit=1