[turba] Re: [Tickets #1814] Improving LDAP support

[Ben Sommer]

bugs at bugs.horde.org wrote:

>DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
>
>Ticket URL: http://bugs.horde.org/ticket/?id=1814
>-----------------------------------------------------------------------
> Ticket             | 1814
> Updated By         | mbydalek at compunetconsulting.com
> Summary            | Improving LDAP support
> Queue              | Turba
> Version            | FRAMEWORK_3
> State              | Unconfirmed
> Priority           | 2. Medium
> Type               | Bug
> Owners             | 
>-----------------------------------------------------------------------
>
>
>mbydalek at compunetconsulting.com (2005-04-20 16:01) wrote:
>
>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 ;)
>  
>
Thanks Mike. I confess to some confused thinking on my part too. I'll 
make one last stab at explaining. If people don't seem interested in the 
changes, I'll have to move on though - I'm busy busy!  :)

Refer to a message I just sent to the turba list regarding my 'magic 
value' RDN:
   

The magic sequence isn't required - only a unique value for the RDN. 
Some user-defined value could be used (like 'mail'). There are certain 
fields that are the purvue of the DSA (e.g. OpenLDAP, or Active 
Directory for non-LDAP geeks) - like timesamp attributes. But I've 
defined an objectclass for use in my addressbook entries, as well as 
other entries, that wants this "magic sequence". I don't need/want my 
clients (i.e. a turba) to know how to genereate that sequence. I just 
want flexibility to, say, pass a code ref to generate the sequence, or 
any other value I might like. Coming from Perl land, we do this all the 
time. That's mainly what I was getting at.

generateUID() is indeed kind of what I want, but I don't want turba (or 
any LDAP client of mine) to know that it needs to use this function for 
anything but its internal use. I just want some reasonable flexibility 
in turba to support my apparently wacky LDAP schema. Being able to 
handle a code ref in ldap.php for the RDN will satisfy that need. I hope 
it can be included!

Thanks,

-- 
Ben Sommer
Senior Technology Officer
Eastern Nazarene College
23 East Elm Ave
Quincy, MA 02170
(617) 745-3817