openldap-technical

openldap-technical@openldap.org

4 participants
9984 discussions

Adding and stating syncrepl via olc
by Bastian Tweddell 19 Feb '26

19 Feb '26

Hi all, I have a question, if there is way that slapd automatically starts syncreplication after it was added to OLC. When installing a fresh slapd with olc config, it starts up with a bootstrap-olc. In the following step the bootstrap process (ansible) reconfigures mostly everything in cn=config, adding globals, ALCs, schema and the main MDB. As soon as the MDB database gets its syncrepl config, the log states it was successful: ``` Config: ** successfully added syncrepl rid=001 "ldaps://PROVIDER01.HOST" Config: ** successfully added syncrepl rid=002 "ldaps://PROVIDER02.HOST" ``` But after that the connections to the providers are not established. Even after waiting way longer then the configured timeout: ``` olcSyncrepl: {0}rid="001" provider="ldaps://PROVIDER01.HOST bind dn="DN_CONSUMER" bindmethod="simple" creden tials="SECRET" filter="(objectclass=*)" keepalive="180:9:75" retry= "20 3 60 10 300 +" schemachecking="on" searchbase="BASEDN " type="refreshAndPersist" olcSyncrepl: {1}rid="002" provider="ldaps://PROVIDER01.HOST bind dn="DN_CONSUMER" bindmethod="simple" creden tials="SECRET" filter="(objectclass=*)" keepalive="180:9:75" retry= "20 3 60 10 300 +" schemachecking="on" searchbase="BASEDN " type="refreshAndPersist" ``` I have to either restart the service or send slapd a SIGUSR1. Is there a way to configure the syncrepl via OLC so that the syncrepl process is initiated automatically when it was added? Many thanks, -- Bastian Tweddell Juelich Supercomputing Centre phone: +49 (2461) 61-6586 --------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------- Forschungszentrum Jülich GmbH 52425 Jülich Sitz der Gesellschaft: Jülich Eingetragen im Handelsregister des Amtsgerichts Düren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Stefan Müller Geschäftsführung: Prof. Dr. Astrid Lambrecht (Vorsitzende), Dr. Stephanie Bauer (stellvertretende Vorsitzende), Prof. Dr. Ir. Pieter Jansens, Prof. Dr. Laurens Kuipers --------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------

2 8

Stupid question about accesslog, delta-syncrepl and efficiency
by Windl, Ulrich 17 Feb '26

17 Feb '26

Hi! Sorry for this stupid question: One argument for delta-syncrepl is that changing a small part of a large object is much more efficient, because pnly the changed data is logged and transferred. However with a multi-valued attributer like pwdHistory the accesslog entry contains all the unchanged values also. E.g.: … reqMod: pwdHistory:+ 20260207170142Z#1.3.6.1.4.1.1466.115.121.1.40#65#{SSHA256 }i56N/G7DutJ3OWdRXDBlSa/7CFN8XLM9X92RwUWohvQiQIEx+cVu9Q== … reqMod: modifyTimestamp:= 20260207170142Z reqOld: pwdHistory: 20240528115526Z#1.3.6.1.4.1.1466.115.121.1.40#38#{SSHA}caF 961AUsh/ECAMdR2i/Iu+DS9Wi22z2 reqOld: pwdHistory: 20240528115715Z#1.3.6.1.4.1.1466.115.121.1.40#38#{SSHA}RSu 8pPgFNIuDP/lBK1qylW+z5aEsr9hD reqOld: pwdHistory: 20240902115523Z#1.3.6.1.4.1.1466.115.121.1.40#38#{SSHA}B8H FVqRKEheQWDonlsu6cyyMH4SNaQOz reqOld: pwdHistory: 20241018115412Z#1.3.6.1.4.1.1466.115.121.1.40#38#{SSHA}9/R BrtPynf5D0cU+R1OGt+ZrdIK4mo0N reqOld: pwdHistory: 20241203075815Z#1.3.6.1.4.1.1466.115.121.1.40#38#{SSHA}raC wwHLscnDFG0SwoH9MBbqI2CCfMlzX reqOld: pwdHistory: 20250115093324Z#1.3.6.1.4.1.1466.115.121.1.40#38#{SSHA}iMd Qy6jvjwtQQXp5JZmAbLovyFsN1b8J reqOld: pwdHistory: 20250124090328Z#1.3.6.1.4.1.1466.115.121.1.40#38#{SSHA}2wQ 4+aXKqOZC1w3uKULFeJ8kleum4Iy6 reqOld: pwdHistory: 20250306085113Z#1.3.6.1.4.1.1466.115.121.1.40#38#{SSHA}aXQ 4DutidnaPGBiitGVAMv8Ebb8YMOOc reqOld: pwdHistory: 20250528131341Z#1.3.6.1.4.1.1466.115.121.1.40#38#{SSHA}YDh Hw94sp0wdjWu9xzm4DKzpUioi5Wqf reqOld: pwdHistory: 20250822074239Z#1.3.6.1.4.1.1466.115.121.1.40#38#{SSHA}Nog FGndg4AiHJEN59Is0JjLgFEx6TQr1 reqOld: pwdHistory: 20250924074514Z#1.3.6.1.4.1.1466.115.121.1.40#65#{SSHA256} lV7mACHa1hPG0RT7EzKM47+EzTz+xamL8+hx72FIG390xyRdnIqkwg== reqOld: pwdHistory: 20250929123923Z#1.3.6.1.4.1.1466.115.121.1.40#65#{SSHA256} kF37AmFjBZFrKeLVjQdemDTi6joE96s4FBhiSqejdSPLdosJVz2YZw== reqOld: pwdHistory: 20251118085003Z#1.3.6.1.4.1.1466.115.121.1.40#65#{SSHA256} f3eB5YSh/xdak80b/eVARKlo/f+vsbD4EbNFv/sfrpbSo2bGfNct6Q== Doesn’t that “cancel” the gain in efficiency? Kind regards, Ulrich Windl

3 4

About Translucent Overlay
by zacc_lxy 12 Feb '26

12 Feb '26

Dear openldap experts, Recently, we are trying to setup a Openldap proxy using translucent overlay. The proxy was configured successfully and we can read remote ldap contents through local proxy. Following the official instruction: https://www.openldap.org/doc/admin24/overlays.html?spm=5176.28103460.0.0.38…, we could see that for the basic attributes we fetched them from remote ldap server, whereas for the new attributes we fetched them from local mdb database. However, we met a special scenario that the instruction didn't mention, and we didn't know how to fulfill it : (1) Assuming there is a user stored in remote ldap server user.ldif dn:uid=user1,ou=People,dc=mydomain,dc=com uid:user1 cn:user1 objectClass:account objectClass:posixAccount objectClass:top objectClass:shadowAccount (2) We would like to add a new attribute in proxy (local mdb database) user_new.ldif dn:uid=user1,ou=People,dc=mydomain,dc=com changetype: modify add: objectClass objectClass: sambaSamAccount The difference was that: the objectClass consists of multiple lines, and account/posixAccount/top/shadowAccount was stored in remote, we just wanted to add a new lines for sambaSamAccount in local mdb. If I execute user_new.ldif then the user1 became that only contained objectClass: sambaSamAccount and account/posixAccount/top/shadowAccount was disappeared. Is there a way to fulfill that ? Thanks, Adrian Liu

2 1

Request for comment: allow ACLs to trigger based on op/controls
by Ondřej Kuzník 12 Feb '26

12 Feb '26

Dear community, for the next release, I've been preparing extensions to the ACL syntax to address a feature request that comes up relatively often - restrict access to data/actions based on what controls are involved. My thinking is that we could allow the following stanzas in the "access to <what>" part: - op=<operation name> or op=<OID> for extended requests - control=<OID> In here, we would probably provide a shorthand for known OIDs using the OID macro in schemas, so you could write something like this: ---- 8< ---- access to dn.subtree=ou=people,dc=example,dc=com attrs=userPassword control=ppolicy by anonymous auth access to dn.subtree=ou=people,dc=example,dc=com attrs=userPassword by group=cn=admin,ou=groups,dc=example,dc=com write by * none ---- 8< ---- As this is a deep change in how people work with ACLs, I'd like some feedback from the community at large before we commit to changing the syntax in a way that we have to live with for a long time. Have you needed something like this? Does the proposed addition solve your use-case? Can you see issues that are not covered or new ones that could crop up when used like this and might not be desirable? Any other feedback or proposals for how this could be expressed are also welcome. I'd like to add that this is unlikely to land until consensus has been achieved in the first place. For those happy to test actual code, the above proposal lives in a merge request: https://git.openldap.org/openldap/openldap/-/merge_requests/720 Thanks, -- Ondřej Kuzník Senior Software Engineer Symas Corporation http://www.symas.com Packaged, certified, and supported LDAP solutions powered by OpenLDAP

1 0

replication deleting users
by steiner＠rutgers.edu 31 Jan '26

31 Jan '26

I'm having an issue with LDAP replication hanging on our AWS ldap users (our master is on prem). So I've been playing with timeouts and keepalive But sometimes when I restart the slapd, it will start to continue replication and then all of a sudden it will start deleting all the users: syncrepl_del_nonpresent: rid=222 be_delete DN (0) and the only way I've found to recover is to stop the slapd, slapcat from the master and slapadd the ldif file into the consumer. Anyone know why this may be happening? Am I missing some setting that I haven't found yet? thanks, ds

2 2

sssd 2.6.3 and openldap 2.5.19 ppolicies
by Felix Natter 30 Jan '26

30 Jan '26

Dear openldap experts, my problem is that my ubuntu 22.04 systems do not honor password expirations (ppolicy/shadow) and ppolicy password complexities. I tried to track this down with AI: * our server does not seem to advertise the OpenLDAP ppolicy control * The ppolicy control OID that SSSD requires (only on Ubuntu, not on RH7) is: 1.3.6.1.4.1.42.2.27.9.5.1 * But your server (OpenlDAP 2.5.19) advertises only these ppolicy‑related controls(?): (ldapsearch -x -H ldap://SERVER -s base -b "" "+") supportedControl: 1.3.6.1.4.1.42.2.27.9.5.8 supportedControl: 1.3.6.1.4.1.42.2.27.8.5.1 * When using ldap_pwd_policy = ppolicy in /etc/sssd/sssd.conf, sssd crashes on startup * this also does not work: ldap_pwd_policy = ppolicy ldap_ppolicy_compat = True Is this train of thought anywhere close to useful? Is there another reason why e.g. passwd(1) ignores password settings on Ubuntu 22.04? Many Thanks and Best Regards, Felix -- Felix Natter debian/rules!

2 2

RE26 testing call (2.6.11) #2
by Quanah Gibson-Mount 29 Jan '26

29 Jan '26

This is the second testing call for OpenLDAP 2.6.11. Depending on the results, this may be the final testing call. Generally, get the code for RE26: <https://git.openldap.org/openldap/openldap/-/archive/OPENLDAP_REL_ENG_2_6/o…> Extract, configure, and build. Execute the test suite (via make test) after it is built. Optionally, cd tests && make its to run through the regression suite. Thanks! OpenLDAP 2.6.11 Engineering Fixed slapd to use fresh timestamp for lastbind (ITS#10379) Fixed slapd delta-syncrepl to always use logDB rootdn (ITS#10360) Fixed slapd reverse lookup of proxied IPv6 addresses (ITS#10387) Fixed slapd logging (ITS#10410) Fixed slapd-ldap response when invalid secprops is configured (ITS#10392) Fixed slapd-mdb error when deleting last child of a branch (ITS#10304) Fixed slapd-mdb check for pool pause in search (ITS#10191) Fixed slapo-memberof clash with refint on subtree rename (ITS#10398) Fixed slapo-syncprov use correct rootDN for accesslog replay (ITS#10385) Minor Cleanup ITS#7901 ITS#10329 ITS#10335 ITS#10339 ITS#10343 ITS#10344 ITS#10345 ITS#10347 ITS#10348 ITS#10349 ITS#10353 ITS#10358 ITS#10359 ITS#10366 ITS#10367 ITS#10369 ITS#10370 ITS#10371 ITS#10372 ITS#10374 ITS#10375 ITS#10376 ITS#10377 ITS#10379 ITS#10380 ITS#10381 ITS#10384 ITS#10388 ITS#10390 ITS#10391 ITS#10400 ITS#10401 ITS#10408 Thanks, Quanah

4 7

Re: [LMDB] Tag problem - update is needed
by Quanah Gibson-Mount 28 Jan '26

28 Jan '26

--On Tuesday, January 27, 2026 2:09 PM +0000 * Neustradamus * <neustradamus(a)hotmail.com> wrote: > Dear OpenLDAP/LMDB team, > > There is an historical problem for Embedded Database LMDB (Lightning > Memory-Mapped Database) source code. > > The latest LMDB version is 0.9.31 (2023-07-10): > - https://github.com/LMDB/lmdb/tags > > Source: > - https://www.symas.com/mdb > > A complete update is possible? > > At the same time, can you change your visibility from "Private" to > "Public"? - https://github.com/orgs/LMDB/people > - https://github.com/orgs/openldap/people > > Note: LMDB 0.9.30 is missing too. Hi, Don't cross post to multiple lists. The official OpenLDAP git repository is at https://git.openldap.org you should be using that. The github location is a mirror that routinely breaks when doing updates. Regards, Quanah

2 2

Error# '-4 Decoding error' with ldap_search_ext_s API
by venugopal chinnakotla 26 Jan '26

26 Jan '26

Hi Team, We are working on migration of nsldap C sdk to OpenLDAP C sdk for our application client code. We are using OpenLDAP 2.6.7. As part of this migration, we are facing one issue related to Decoding Error while making ldap_search_ext_s API under load. OpenLDAP C SDK API ldap_search_ext_s is giving -4 : Decoding error when we are making a search call to LDAP server (with SSL and without SSL) under load with multi threading. Here are few log messages related to -4: decoding error [10052/17636][ERROR]Error# '-4' during search: 'error: Decoding error' Search Query = '(cn=user1)' for server 'ldapserver1:10001' [10052/15624][ERROR]Error# '-4' during search: 'error: Decoding error' Search Query = '(cn=user2)' for server 'ldapserver1:10001' When we run the same load with NSLDAP, we are not getting any Decoding errors. Whenever we switch to OpenLDAP APIs and run the load, we are getting Decoding errors for few transactions under the load. Could you please look into this and provide any solution available for this issue? Thank you. -- Thanks, *c.venugopal*

4 3

[LMDB] Nested transactions
by Stefano Cossu 18 Jan '26

18 Jan '26

Hi there, I am trying to create a nested RW transaction under a RO transaction in LMDB v0.9.33: int nested_op (MDB_env *env, MDB_txn *th) { MDB_txn *ptxn, *txn; if (th) ptxn = th; else mdb_txn_begin (env, NULL, MDB_RDONLY, &ptxn); return mdb_txn_begin (env, ptxn, 0, &txn); } (rc checks skipped in example) th can be NULL or an existing open transaction. It may be RW or RO. If I run this code, the second mdb_txn_begin call fails with EINVAL. If I set the parent in that call to NULL, it succeeds. I verified that env is healthy and I can open other transactions in it; in fact, the first mdb_txn_begin succeeds. According to the manual, I should be able to do this. Is the sample code correct? Thanks, Stefano

2 2

← Newer
1
2
3
4
5
6
7
...
999
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openldap-technical