On Thu, Mar 27, 2025 at 12:07:23PM +0000, Windl, Ulrich wrote:
> I thought I had explained my thoughts:
>
> I understand that braces are needed to _order_ multi-valued attributes
> (the "entries" within the parent), but I don't understand wha the
> braces are needed for an attribute that is single-valued (thus there
> is no ordering possible). For example: olcOverlay is SINGLE-VALUE
> (there may be only one overlay in an olcOverlayConfig object).
They are needed to order the entry among its siblings. If you had two or
more overlays, you need to describe where they stand compared to each
other in the overlay stack. As I said, read up on how
"X-ORDERED 'SIBLINGS'" attributes work if this summary is not enough.
> So why is this wrong then?:
> dn: olcOverlay={1}accesslog,olcDatabase={0}config,cn=config
> objectClass: olcOverlayConfig
> objectClass: olcAccessLogConfig
> olcOverlay: accesslog
The value "{1}accesslog" is not present in the entry despite
"olcOverlay={1}accesslog" used in the RDN. That would be a violation of
what the RFC451x series requires a DIT conforming with LDAP to maintain.
Both of the above have been mentioned in previous emails in this thread,
so again: can you explain what it is that you mean?
Thanks,
--
Ondřej Kuzník
Senior Software Engineer
Symas Corporation http://www.symas.com
Packaged, certified, and supported LDAP solutions powered by OpenLDAP
