dorian taylor wrote:
[..], and the entryUUID attribute itself is constrained in the schema [3] to not permit modification (where "modification" ostensibly also extends to adding new records).
A client application can set 'entryUUID' by sending the relax rules control along with the add/modify request.
I used this in a migration project deriving OpenLDAP's entryUUID from Novell eDirectory's GUID.
Of course the client app is then responsible for generating proper UUIDs. With random UUIDs you might run out of entropy depending on how many you have to generated within a certain time.
Ciao, Michael.