<?xml version="1.0" encoding="utf-8" ?>
<rss version="2.0">
<channel>
<title>Fun with ones and zeros - openldap</title>
<description><![CDATA[Barry's notes on computer software and hardware]]></description>
<link>/blog/tags/openldap</link>
<lastBuildDate>Wed, 17 Jun 2026 01:52:53 -0700</lastBuildDate>
<item>
<title>OpenLDAP entryUUID generation
</title>
<link>/blog/entries/openldap_uuid</link>
<pubDate>Fri, 09 Jun 2006 07:42:00 -0700</pubDate>
<author>bp@barryp.org (Barry Pederson)</author>
<description><![CDATA[
<p>
At work I'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's been holding me up is that
it wasn't obvious at all how <code>entryUUID</code> and <code>entryCSN</code>
attributes get generated.
</p>
<p>
Turns out that if you have <code>lastmod off</code> in your <code>slapd.conf</code>, 
as I did, that seems to suppress generating those attributes, in addition to the 
ones that are actually documented (modifiersName, modifyTimestamp, ...).  I had left 
<code>lastmod off</code> because I was getting info from an Netscape Directory Server, 
which already put in that info, and didn't want OpenLDAP messing with it.  Turns out 
that wasn't a concern, and from what I can tell from the sourcecode, OpenLDAP only
adds modification attributes if they don't already exist.
</p>
<p>
Overall I've been pretty frustrated with OpenLDAP documentation through the years, 
and reading the sourcecode isn't much better, since comments at least
in the files I looked at are sparse to nonexistant.  
</p>



]]></description>
</item>
</channel>
</rss>