I believe the fix for bug 2027 covers what Mike is talking about, in 
that the UID can be used in the DN. Given that I'm closing this ticket 
since I believe what needs to be addressed is addressed. More can even 
probably be done with hooks if necessary.

Hi Ben,



I remember reading your initial posting to the list a week ago, and 
something didn't sit right with me in terms of what you were saying.   
I partially agreed, but partially didn't, and finally I had some time 
to sit down and look at some code.



Basically, I agree with what you are saying about having a 'cn' as the 
RDN, it just won't work.  But, there already is a generateUID() 
function which can be used.  Rather than modifying all the existing 
code, just changing the order of add() in Driver.php should do the 
trick.



I'm not sure how this would affect other drivers, but if you can get 
in $attributes the 'dn' (incorrectly named, should be 'rdn' as you 
pointed out) for when you do the _makeKey() call, you could use that 
to set your dn giving you a perfectly unique entry each time.



I hope some of this makes sense as it does get confusing after looking 
at it for a while ;)



-Mike

...and the second file...

This patch corrects an assumption about LDAP in turba that an RDN can 
be multi-valued. It also adds support for specifying an auto-generated 
value for an addressbook entry;s RDN. This is done via an anonynmous 
function created and configured in 'config/sources.php'. Code in 
lib/Driver/ldap.php that is no longer is needed after this patch was 
removed.