openldap-technical

openldap-technical@openldap.org

7 participants
9864 discussions

2.5 Quick-Start guide roadblock: ldap_bind: Confidentiality required (13)
by Ben Poliakoff 23 Feb '22

23 Feb '22

I've been using the Symas OpenLDAP debian packages, and following the Quick-Start guide for 2.5: https://www.openldap.org/doc/admin25/quickstart.html Following steps 1 - 10 has been straight forward, but when I get to step 11 (Add initial entries to your directory), I run into trouble when running the ldapadd command: root@openldap-x:/opt/symas/etc/openldap# ldapadd -x -D "cn=Manager,dc=example,dc=com" -W -f bootstrap.ldif Enter LDAP Password: ldap_bind: Confidentiality required (13) additional info: confidentiality required root@openldap-x:/opt/symas/etc/openldap# I used the provided slapd.ldif.default to seed the cn=config (updating it with the appropriate domain components), as per the instructions in the Quick-Start, so slapd isn't yet configured to run with ssl or starttls. Is there a default SSF factor that I should adjust to get past this bootstrapping failure? I don't see anything like that explicitly set in the configs that were rendered into /opt/symas/etc/openldap/slapd.d, from my slapd.ldif. I'm not new to openldap, but this is the first time I've used the Symas packages and also the first time trying to use olc instead of a slapd.conf based configuration. Ben

2 1

OpenLdap on Rocky 8 -- suggestions?
by Aaron Bennett 23 Feb '22

23 Feb '22

Hi, I'm migrating a small two-node OpenLDAP cluster from CentOS 7 to Rocky 8. I've been maintaining my own openldap rpms forked off of the RHEL 7 srpms, edited to link against OpenSSL instead of the never-to-be-sufficiently-d*mned GnuTLS. Now that there is no official openldap build from RedHat, I'm evaluating my choices. Essentially it comes down to these: 1. Build from source every time. Not difficult and I'm comfortable with it, but I prefer when possible to not drop non-rpm packaged files into production 2. Package it myself. If we still used it super extensively like we did in the past, I would do this, but it's a lot of work. 3. Look for third-party packages that are frequently updated. My preference is 3, which of course leads me to Symas OpenLdap. Looking at the symas page, it looks like there are two branches, the LTS 2.5 branch and the 2.6 branch. If this is accurate and the 2.5 branch is updated with security backports, etc, and is still gratis, that's the direction I'm looking to go. Any gotchas, or am I totally missing something obvious? Best, Aaron Bennett --- Aaron Bennett Manager of Systems Administration Clark University ITS

2 1

Re: log analysis tools
by Clément OUDOT 22 Feb '22

22 Feb '22

Le sam. 5 févr. 2022 à 20:57, Quanah Gibson-Mount <quanah(a)fast-mail.org> a écrit : > > > --On Friday, February 4, 2022 10:12 PM -0500 Dave Macias <davama(a)gmail.com> > > wrote: > > > > > > > https://www.ltb-project.org/documentation/ldap-stats.html > > Is that the one I used to help maintain? I don't believe it's been updated > for 2.5 and later, unless it was forked and someone else has started > working on it. > Hello Quanah, this is indeed a fork done inside LTB project, there was no git repo for this script (or I did not found it). Of course if there are changes in 2.5 log format, we can update the script. Clément.

4 8

str2entry: invalid value for attributeType objectClass #1 (syntax 1.3.6.1.4.1.1466.115.121.1.38)
by gpaz＠iter.es 21 Feb '22

21 Feb '22

````` [root@ldap ~]# slapcat The first database does not allow slapcat; using the first available one (2) dn: dc=ldap,dc=test objectClass: top objectClass: dcObject objectClass: organization dc: ldap o: ldap_test_iter description: ldap_test_iter structuralObjectClass: organization entryUUID: 4a04a984-1dfc-103c-8835-d781e468857b creatorsName: cn=Manager,dc=ldap,dc=test createTimestamp: 20220209135948Z entryCSN: 20220209135948.842285Z#000000#000#000000 modifiersName: cn=Manager,dc=ldap,dc=test modifyTimestamp: 20220209135948Z dn: ou=users,dc=ldap,dc=test objectClass: organizationalUnit ou: users structuralObjectClass: organizationalUnit entryUUID: 4a09e624-1dfc-103c-8836-d781e468857b creatorsName: cn=Manager,dc=ldap,dc=test createTimestamp: 20220209135948Z entryCSN: 20220209135948.876561Z#000000#000#000000 modifiersName: cn=Manager,dc=ldap,dc=test modifyTimestamp: 20220209135948Z dn: ou=groups,dc=ldap,dc=test objectClass: organizationalUnit ou: groups structuralObjectClass: organizationalUnit entryUUID: 4a0dc5fa-1dfc-103c-8837-d781e468857b creatorsName: cn=Manager,dc=ldap,dc=test createTimestamp: 20220209135948Z entryCSN: 20220209135948.901999Z#000000#000#000000 modifiersName: cn=Manager,dc=ldap,dc=test modifyTimestamp: 20220209135948Z dn: uid=pedro,ou=users,dc=ldap,dc=test uid: pedro cn: pedro sn: pedro objectClass: top objectClass: posixAccount objectClass: inetOrgPerson loginShell: /bin/bash uidNumber: 500 gidNumber: 500 mail: pedro(a)example.com gecos: pedro user homeDirectory: /home/pedro structuralObjectClass: inetOrgPerson entryUUID: 908089be-1dfc-103c-8838-d781e468857b creatorsName: cn=Manager,dc=ldap,dc=test createTimestamp: 20220209140147Z userPassword:: e1NTSEF9eWdWaGZSMFhKY3N3blpLREdMbm9TU0VlanVWK01jL0s= entryCSN: 20220217123622.452494Z#000000#000#000000 modifiersName: uid=pedro,ou=users,dc=ldap,dc=test modifyTimestamp: 20220217123622Z dn: cn=pedro,ou=groups,dc=ldap,dc=test objectClass: posixGroup objectClass: top cn: pedro userPassword:: e2NyeXB0fXg= gidNumber: 500 memberUid: uid=pedro structuralObjectClass: posixGroup entryUUID: 9096c90e-1dfc-103c-8839-d781e468857b creatorsName: cn=Manager,dc=ldap,dc=test createTimestamp: 20220209140147Z entryCSN: 20220209140147.240435Z#000000#000#000000 modifiersName: cn=Manager,dc=ldap,dc=test modifyTimestamp: 20220209140147Z dn: cn=module,dc=ldap,dc=test cn: module objectClass: top objectClass: olcModuleList olcModuleLoad: ppolicy.la olcModulePath: /usr/lib64/openldap structuralObjectClass: olcModuleList entryUUID: 8ffa80b4-243f-103c-809a-d143605cbb0e creatorsName: cn=Manager,dc=ldap,dc=test createTimestamp: 20220217131629Z entryCSN: 20220217131629.473761Z#000000#000#000000 modifiersName: cn=Manager,dc=ldap,dc=test modifyTimestamp: 20220217131629Z dn: ou=ppolicy,dc=ldap,dc=test objectClass: organizationalUnit ou: ppolicy structuralObjectClass: organizationalUnit entryUUID: aeeed796-2443-103c-9d36-4f3e029afe7a creatorsName: cn=Manager,dc=ldap,dc=test createTimestamp: 20220217134559Z entryCSN: 20220217134559.393630Z#000000#000#000000 modifiersName: cn=Manager,dc=ldap,dc=test modifyTimestamp: 20220217134559Z ````` When I try enable the modulo I obtain the next error: ````` [root@ldap ldap]# slapadd -n2 -l 2.2_ppolicy-bdb-ldap.test.ldif str2entry: invalid value for attributeType objectClass #1 (syntax 1.3.6.1.4.1.1466.115.121.1.38) slapadd: could not parse entry (line=1) _#################### 100.00% eta none elapsed none fast! Closing DB... ````` File 2.2_ppolicy-bdb-ldap.test.ldif: ````` [root@ldap ldap]# cat 2.2_ppolicy-bdb-ldap.test.ldif dn: olcOverlay=ppolicy,olcDatabase={2}bdb,cn=config objectClass: olcOverlayConfig objectClass: olcPPolicyConfig olcOverlay: ppolicy olcPPolicyDefault: cn=default,ou=ppolicy,dc=ldap,dc=test olcPPolicyUseLockout: TRUE olcPPolicyHashCleartext: TRUE ````` Could anyone help me?

2 3

slapcat truncates slapd.log
by Jose Garcia 21 Feb '22

21 Feb '22

Hello, openldap.org community! This is my first thread here, in the hopes of finding a better understanding of a problem I'm having with OpenLDAP after several hours of unsuccessful troubleshooting. I'm in no way an expert on the matter so maybe someone more experienced here could help me get things a bit clearer. I recently found this issue in two Ubuntu 18.04 servers I'm running with OpenLDAP 2.4 and bdb backend for their databases. I want to export my LDAP database to an LDIF file by running: # slapcat -l database.ldif This works just fine. However, I realized every time I run such slapcat command, my slapd.log file gets truncated (i.e. all previous log entries are deleted). This happens on both servers, no matter if the slapd daemon is running or not. I don't know if this is normal or expected behavior, but it is weird to me that slapcat is wiping the log files. From what I understood slapd is in charge of the logging, so why is slapcat messing with that? Is this just normal/expected behavior, or am I experiencing some kind of weird issue here?

2 1

RE: Error when running make test or slapd after building on windows
by Joshua Dunbar 21 Feb '22

21 Feb '22

I see this issue here as well: https://www.mail-archive.com/openldap-bugs@openldap.org/msg08059.html But not sure I understand what the resolution is -----Original Message----- From: Joshua Dunbar Sent: Friday, February 18, 2022 11:19 AM To: Howard Chu <hyc(a)symas.com>; Dr. Ogg <ogg(a)sr375.com> Cc: Quanah Gibson-Mount <quanah(a)fast-mail.org>; openldap-technical(a)openldap.org Subject: RE: Error when running make test or slapd after building on windows I've attached the config.log -----Original Message----- From: Joshua Dunbar Sent: Friday, February 18, 2022 11:12 AM To: 'Howard Chu' <hyc(a)symas.com>; 'Dr. Ogg' <ogg(a)sr375.com> Cc: 'Quanah Gibson-Mount' <quanah(a)fast-mail.org>; 'openldap-technical(a)openldap.org' <openldap-technical(a)openldap.org> Subject: RE: Error when running make test or slapd after building on windows I installed Msys and ran the pacman commands via the instructions here: https://www.msys2.org/. I then opened a MSYS MinGW 64-bit command prompt and ran configure, make depend, and make. Make ends with the following error C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/11.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: .libs/os-ip.o: in function `ldap_int_poll': C:/Users/USAF_Admin/Desktop/openldap-2.6.1/openldap-2.6.1/libraries/libldap/os-ip.c:391: undefined reference to `ber_pvt_wsa_err2string' collect2.exe: error: ld returned 1 exit status make[2]: *** [Makefile:437: libldap.la] Error 1 make[2]: Leaving directory '/home/USAF_Admin/libraries/libldap' make[1]: *** [Makefile:312: all-common] Error 1 make[1]: Leaving directory '/home/USAF_Admin/libraries' make: *** [Makefile:320: all-common] Error 1 Any ideas? -----Original Message----- From: Joshua Dunbar Sent: Thursday, February 17, 2022 6:17 PM To: Howard Chu <hyc(a)symas.com>; Dr. Ogg <ogg(a)sr375.com> Cc: Quanah Gibson-Mount <quanah(a)fast-mail.org>; openldap-technical(a)openldap.org Subject: RE: Error when running make test or slapd after building on windows Unfortunately this is for a government contract project and we are being mandated to use windows and not a containerized environment. Docker for windows was also booted. I have MSYS installed, as well as latest openldap source. -----Original Message----- From: Howard Chu <hyc(a)symas.com> Sent: Thursday, February 17, 2022 6:06 PM To: Dr. Ogg <ogg(a)sr375.com>; Joshua Dunbar <jdunbar(a)montereytechnologies.com> Cc: Quanah Gibson-Mount <quanah(a)fast-mail.org>; openldap-technical(a)openldap.org Subject: Re: Error when running make test or slapd after building on windows Dr. Ogg wrote: > Why not run in a Linux VM or a docker container? and avoid Cygwin? Or WSL2. I hear that works pretty well these days. > > >> On Feb 17, 2022, at 2:48 PM, Joshua Dunbar <jdunbar(a)montereytechnologies.com> wrote: >> >> Are there up to date instructions on how to build with Cygwin or Msys somewhere? I am trying to do this on a 64 bit Windows 10 computer. The way I am doing it with Cygwin with default configure options must be wrong. I am new to both Cygwin and OpenLDAP so apologies for my inexperience. >> >> -----Original Message----- >> From: Howard Chu <hyc(a)symas.com> >> Sent: Thursday, February 17, 2022 5:40 PM >> To: Quanah Gibson-Mount <quanah(a)fast-mail.org>; Joshua Dunbar >> <jdunbar(a)montereytechnologies.com>; openldap-technical(a)openldap.org >> Subject: Re: Error when running make test or slapd after building on >> windows >> >> Quanah Gibson-Mount wrote: >>> >>> >>> --On Thursday, February 17, 2022 8:00 PM +0000 Joshua Dunbar <jdunbar(a)montereytechnologies.com> wrote: >>> >>>> >>>> >>>> Hello, >>>> >>>> >>>> >>>> I am attempting to install openldap (latest version 2.6.1) on >>>> windows using Cygwin where I have installed dependencies of gcc >>>> core and make in order to get configure to run. I then run >>>> configure from a Cygwin terminal (without any arguments). Configure >>>> seems to run fine, and so does make depend, and make. Then when I >>>> attempt to run make test (or slapd with any other well formatted >>>> slapd.conf file) I get the following error message. I >>> >>> Hi Joshua, >>> >>> It's likely related to this discussion: >>> >>> <https://cygwin.com/pipermail/cygwin/2019-July/241961.html> >> >> More than just that. OpenLDAP code supports real POSIX environments and native WIN32 environments. >> It doesn't support Cygwin, which is a partially-working fake POSIX environment. >> >> You can use Cygwin or MSYS as the build platform, but the binaries will only work if built with the MinGW toolchain for native WIN32 output. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

3 5

Setup password policies: problem when adding OU
by Felix Natter 19 Feb '22

19 Feb '22

hello, I am trying to setup PPs using this guide: https://tylersguides.com/guides/openldap-password-policy-overlay/ Everything went fine up to adding the OU for the PP: policyou.ldif: dn: ou=policies,dc=company,dc=com objectClass: organizationalUnit ou: policies ldapadd -Y EXTERNAL -Q -H ldapi:/// -f policyou.ldif (1) which results in https://ldapwiki.com/wiki/LDAP_INSUFFICIENT_ACCESS (with "additional info: no write access to parent") Now I tried _several_ commands to fix this, then I did: ldapadd -H ldapi:/// -D cn=admin,cn=config -W -f policyou.ldif (2) which works. But I have to fix this on the production server now, and I don't know whether (2) fixed this or some other command. What could be the problem with (1)? Previously I used this guide to change the admin password twice: https://www.digitalocean.com/community/tutorials/how-to-change-account-pass… Do I have to set the password for cn=admin,cn=config separately? If yes, could you suggest a HOWTO? Many Thanks and Best Regards, Felix -- Felix Natter

3 4

Re: Error when running make test or slapd after building on windows
by Howard Chu 18 Feb '22

18 Feb '22

Dr. Ogg wrote: > Why not run in a Linux VM or a docker container? and avoid Cygwin? Or WSL2. I hear that works pretty well these days. > > >> On Feb 17, 2022, at 2:48 PM, Joshua Dunbar <jdunbar(a)montereytechnologies.com> wrote: >> >> Are there up to date instructions on how to build with Cygwin or Msys somewhere? I am trying to do this on a 64 bit Windows 10 computer. The way I am doing it with Cygwin with default configure options must be wrong. I am new to both Cygwin and OpenLDAP so apologies for my inexperience. >> >> -----Original Message----- >> From: Howard Chu <hyc(a)symas.com> >> Sent: Thursday, February 17, 2022 5:40 PM >> To: Quanah Gibson-Mount <quanah(a)fast-mail.org>; Joshua Dunbar <jdunbar(a)montereytechnologies.com>; openldap-technical(a)openldap.org >> Subject: Re: Error when running make test or slapd after building on windows >> >> Quanah Gibson-Mount wrote: >>> >>> >>> --On Thursday, February 17, 2022 8:00 PM +0000 Joshua Dunbar <jdunbar(a)montereytechnologies.com> wrote: >>> >>>> >>>> >>>> Hello, >>>> >>>> >>>> >>>> I am attempting to install openldap (latest version 2.6.1) on windows >>>> using Cygwin where I have installed dependencies of gcc core and make >>>> in order to get configure to run. I then run configure from a Cygwin >>>> terminal (without any arguments). Configure seems to run fine, and so >>>> does make depend, and make. Then when I attempt to run make test (or >>>> slapd with any other well formatted slapd.conf file) I get the >>>> following error message. I >>> >>> Hi Joshua, >>> >>> It's likely related to this discussion: >>> >>> <https://cygwin.com/pipermail/cygwin/2019-July/241961.html> >> >> More than just that. OpenLDAP code supports real POSIX environments and native WIN32 environments. >> It doesn't support Cygwin, which is a partially-working fake POSIX environment. >> >> You can use Cygwin or MSYS as the build platform, but the binaries will only work if built with the MinGW toolchain for native WIN32 output. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

2 2

DNS/ldap
by pascal.jakobi＠gmail.com 18 Feb '22

18 Feb '22

Just a question (quick). You probably saw the relatively new CAA record for DNS. This (great) record provides a means to get the address of a CA for a given DNS domain. Firstly, it is unclear to me why the old SRV records are not used as they essentially do the same. You may think of creating an SRV record for _pkica.<domain> that would provide a CA's IP address. Then my question is : why is this SRV not used on linux boxes ? This would provide a means to retrieve automatically a certificate/public key for a given user and avoid setting configs (i.e. ldap.conf) on the client side. In other tertms, don't we need a CAA equivalent for Directories ?

1 0

Error when running make test or slapd after building on windows
by Joshua Dunbar 17 Feb '22

17 Feb '22

Hello, I am attempting to install openldap (latest version 2.6.1) on windows using Cygwin where I have installed dependencies of gcc core and make in order to get configure to run. I then run configure from a Cygwin terminal (without any arguments). Configure seems to run fine, and so does make depend, and make. Then when I attempt to run make test (or slapd with any other well formatted slapd.conf file) I get the following error message. I have turned on the highest level of logging and don't get any additional useful information and have been going at this for a couple days now without any luck. I have tried manipulating permissions on the db folder as well as using different folder names and locations. I can see the lock.mdb file being generated in the /tests/testrun/db.1.a folder, but nothing else. Any insight or help would be very appreciated. 620dab00.2d2e09dc 0x800000010 config_build_entry: "olcDatabase={2}monitor" 620dab00.2d2e359c 0x800000010 slap_get_csn: conn=-1 op=0 generated new csn=20220217015512.758001Z#000000#000#000000 manage=0 620dab00.2d2ecdf4 0x800000010 backend_startup_one: starting "o=OpenLDAP Project,l=Internet" 620dab00.2d2edba0 0x800000010 mdb_db_open: "o=OpenLDAP Project,l=Internet" 620dab00.2d3072a8 0x800000010 mdb_db_open: database "o=OpenLDAP Project,l=Internet": dbenv_open(/tests/testrun/db.1.a). 620dab00.2d3a1894 0x800000010 mdb_db_open: database "o=OpenLDAP Project,l=Internet" cannot be opened: Invalid argument (22). Restore from backup! 620dab00.2d3a37d4 0x800000010 backend_startup_one (type=mdb, suffix="o=OpenLDAP Project,l=Internet"): bi_db_open failed! (22) 620dab00.2d3a42c4 0x800000010 slapd shutdown: initiated 620dab00.2d3c25f8 0x800000010 slapd destroy: freeing system resources. 620dab00.2d5278d0 0x800000010 slapd stopped. Thanks, Josh

3 4

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openldap-technical