<?xml version="1.0" encoding="utf-8" ?>
<feed xmlns="http://www.w3.org/2005/Atom">
<title>Fun with ones and zeros - openldap</title>
<subtitle>Barry&#039;s notes on computer software and hardware</subtitle>
<link href="/blog/tags/openldap"></link>
<updated>2026-06-17T01:49:07-07:00</updated>
<id>urn:uuid:75c95eec-a4e9-fdc8-80d8-340d53fceb0a</id>
<entry>
<title>OpenLDAP entryUUID generation
</title>
<link href="/blog/entries/openldap_uuid"></link>
<id>urn:uuid:e8a59f5a-6513-b5fa-59e8-766434f25aa2</id>
<updated>2006-06-09T07:42:00-07:00</updated>
<author><name>Barry Pederson</name>
<email>bp@barryp.org</email>
</author>
<content type="html">
&lt;p&gt;
At work I&#039;ve been fighting with OpenLDAP, hoping to update some really
old servers (as in 2.0.xx), and possibly using syncrepl instead of slurpd
to replicate between servers.  One thing that&#039;s been holding me up is that
it wasn&#039;t obvious at all how &lt;code&gt;entryUUID&lt;/code&gt; and &lt;code&gt;entryCSN&lt;/code&gt;
attributes get generated.
&lt;/p&gt;
&lt;p&gt;
Turns out that if you have &lt;code&gt;lastmod off&lt;/code&gt; in your &lt;code&gt;slapd.conf&lt;/code&gt;, 
as I did, that seems to suppress generating those attributes, in addition to the 
ones that are actually documented (modifiersName, modifyTimestamp, ...).  I had left 
&lt;code&gt;lastmod off&lt;/code&gt; because I was getting info from an Netscape Directory Server, 
which already put in that info, and didn&#039;t want OpenLDAP messing with it.  Turns out 
that wasn&#039;t a concern, and from what I can tell from the sourcecode, OpenLDAP only
adds modification attributes if they don&#039;t already exist.
&lt;/p&gt;
&lt;p&gt;
Overall I&#039;ve been pretty frustrated with OpenLDAP documentation through the years, 
and reading the sourcecode isn&#039;t much better, since comments at least
in the files I looked at are sparse to nonexistant.  
&lt;/p&gt;



</content>
</entry>
</feed>