[turba] Re: turba ldap driver

[Adam Tauno Williams]

> Also, my confusion about whether turba could be configured to work with 
> this schema was compounded by the param 'dn', which is misnamed. It 
> should be 'rdn', and its value should not be an array - since an RDN is 
> by definition _one_ attribute.

You're wrong.  Multi-valued RDNs are legal, and not that uncommon, in LDAP.

> Second, the capability to make the RDN attribute non-user defined should 
> be added to the driver and the config/sources.php examples. Reasoning is 
> the same here too - the RDN must be unique, and therefore 
> system-generated - just like an auto-incremented ID in an SQL database. 
> We kinda have the right idea in lib/Driver.php with '__uid', but this 
> should be configurable from within an LDAP turba data source. (The use 
> of the name 'uid' here was another confuser!)
> That's all. What do you think?

This sounds more like a job for the DSA than for the client;  otherwise only the
Turba client can add objects and get your magic sequence.