[phpldapadmin] [ phpldapadmin-Feature Requests-2665544 ] save allows uidNumber to be non-unique

"SourceForge.net" <[email protected]>
Newsgroups gmane.comp.ldap.davedap
Message-ID <[email protected]>
Feature Requests item #2665544, was opened at 2009-03-06 02:51
Message generated for change (Comment added) made by wurley
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=498549&aid=2665544&group_id=61828

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: Charles Johnson (ironslammer)
Assigned to: Nobody/Anonymous (nobody)
Summary: save allows uidNumber to be non-unique

Initial Comment:
When multiple persons are adding users it is possible that the uidNumber of an entry is saved to more than one entry.

This can be reproduced by two administrators creating users as the same time.  When the add entry screen appears, the uidNumber automatically increments to a unique uidNumber.  If two admins do this at the same time their screen will have the same uidNumber.  If one admin saves before the other, PLA does not warn that the uidNumber already exists when the second admin does their save. 

----------------------------------------------------------------------

>Comment By: Deon George (wurley)
Date: 2009-03-20 18:23

Message:
This is a well known race condition, and not really a problem that PLA
should address.

PLA is an LDAP administration tool, not a "user admin" tool, however we do
do some extra things to make administering LDAP data easier. This condition
cannot really be architecturely implemented nicely - it has been discussed
on the mailling list in the past.

The only true arbitrator of duplicate data should be the server itself (I
believe openLDAP has modules to address that).

If PLA was to address this problem, then a mechanism needs to be setup,
where we can write to the server, (obtaining "a lock"), get our unique
entry value, submit it, and release "our lock". In addition, we then need
to handle stale locks, etc...

I'll move this over to a feature request, in case somebody wants to write
it :)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=498549&aid=2665544&group_id=61828

------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
______________________________________
phpLDAPadmin development mailing list.
To unsbuscribe: https://lists.sourceforge.net/lists/listinfo/phpldapadmin-devel
http://phpldapadmin.sourceforge.net/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.