openldap-technical December 2020

openldap-technical@openldap.org

21 participants
22 discussions

verify openldap source
by A. Schulze 16 Dec '20

16 Dec '20

Hello, I'm searching for a way to verify the integrity of downloads from openldap.org. Many open source projects use to provide foo-$version.tar.gz.[asc|sha256sum] next to foo-$version.tar.gz Is something similar available for openldap? Andreas

3 4

new index on consumer
by Stefan Kania 10 Dec '20

10 Dec '20

Hello If I create a new index on a provider in slapd.conf NOT in cn=config (using mdb). I have to do a slapindex on the provider. When I configure the same index in consumer slapd.conf do I have to do the slapindex here too? Greeting Stefan --

2 1

Symas OpenLDAP for Linux Ubuntu PPA (18 LTS, 20 LTS)
by Quanah Gibson-Mount 09 Dec '20

09 Dec '20

Symas is now producing a PPA for Symas OpenLDAP for Linux on the Ubuntu platform. Packages can be obtained from: <https://launchpad.net/~symas/+archive/ubuntu/sofl/> The PPA build keeps all Ubuntu modifications (such as building nssov, etc). Regards, Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

Changes to CentOS project
by Quanah Gibson-Mount 09 Dec '20

09 Dec '20

In case people missed it, the CentOS project is changing how it operates, and changing the EOL for CentOS8 from 2029 to the end of 2021: <https://blog.centos.org/2020/12/future-is-centos-stream/> Symas plans to continue to produce packages suitable for CentOS7 and CentOS8 until their respective EOLs, and to continue to provide packages for RHEL7 and RHEL8 until their EOLs. Regards, Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

Reset admin pass
by Клеусов Владимир Сергеевич 09 Dec '20

09 Dec '20

Hi. How do I change the admin password correctly and not break replication ? =) here when setting up replication the password was mentioned dn: olcDatabase={0}config,cn=config changetype: modify add: olcRootPW olcRootPW: 123 And dn: olcDatabase={0}config,cn=config changetype: modify replace: olcSyncRepl olcSyncRepl: rid=001 provider=ldaps://ldap1.domain.com searchbase="cn=config" bindmethod=simple credentials=123 binddn="cn=admin,cn=config" tls_reqcert=never type=refreshAndPersist retry="30 +" timeout=1 olcSyncRepl: rid=002 provider=ldaps://ldap2.domain.com searchbase="cn=config" bindmethod=simple credentials=123 binddn="cn=admin,cn=config" tls_reqcert=never type=refreshAndPersist retry="30 +" timeout=1 tls_reqcert=never type=refreshAndPersist retry="5 5 300 5" timeout=1 - replace: olcMirrorMode olcMirrorMode: TRUE

3 15

objectclass for organizationIdentifier?
by mark 08 Dec '20

08 Dec '20

Hi all, while creating directory entries in OpenLDAP I am struggling with the attribute organizationIdentifier (OID 2.5.4.97). The main problem: there seems to be no standard objectClass that contains this attribute (i.e. not in X.521). This has already been discussed in this thread from 2017: https://www.openldap.org/lists/openldap-technical/201701/msg00075.html. I would like to avoid creating my own custom auxiliary class when possible. Is anybody aware of (or has created) an existing object class for this attribute? - Mark

1 0

Failing "id uid" test
by armin.vehr＠mmlab.de 06 Dec '20

06 Dec '20

Hi ML! I have set up an OpenLDAP server with TLS/SSL support from the repositories. The platform is Debian 10. I followed this guide: https://kifarunix.com/setup-openldap-server-with-ssl-tls-on-debian-10/ Now I want to use the LDAP users on a CentOS 8 client, so I followed this guide in order to set up the LDAP authentication mechanisms: https://kifarunix.com/configure-sssd-for-openldap-authentication-on-centos-… The current state is that I get the following message returned when I try to check an LDAP user's ID on the client system: [root@myldapclient ~]# id testuser id: `testuser´: no such user Obviously sth. is malconfigured. At least enumerating all LDAP objects works on the client. The command ldapsearch -h myldapserver.mycompany.mytld -x -D "cn=readonlybind,dc=mycompany,dc=mytld" -W -LLL -b "dc=mycompany,dc=mytld" returns all of the LDAP's objects. I'd appreciate hints how to track the issue down. First: What is the default LDAP log on Debian 10 or how can I determine an alternative log, if this is recommended? Thank you! __________ Information from mm-lab IT security __________The message was checked by ESET Mail Security.

2 1

sharing transactions across threads
by James Anderson 04 Dec '20

04 Dec '20

the mdb_env_open documentation includes in its note about NOTLS, that A read-only transaction may span threads if the user synchronizes its use. to which read-only operations would this constraint apply? mdb_cursor_open and mdb_cursor_close look as if they modify transaction state for write transactions only. best regards, from berlin

5 11

Other error (80) when adding olcTLSCipherSuite
by Benjamin Schneider 03 Dec '20

03 Dec '20

Hi all, I'm running version 2.4.49 on Ubuntu 20.04. I've been unable to add the olcTLSCipherSuite configuration attribute. # ldapmodify -H ldapi:// -Y EXTERNAL -f set-ciphersuite.ldif returns: SASL/EXTERNAL authentication started SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth SASL SSF: 0 modifying entry "cn=config" ldap_modify: Other (e.g., implementation specific) error (80) set-ciphersuite.ldif contains the following: dn: cn=config changetype: modify add: olcTLSCipherSuite olcTLSCipherSuite: ALL I was able to successfully configure (and confirmed working) TLS by setting the following attributes: olcTLSCACertificateFile: /etc/ssl/certs/mydomain.fullchain.pem olcTLSCertificateFile: /etc/ssl/certs/mydomain.cert.pem olcTLSCertificateKeyFile: /etc/ssl/private/mydomain.privkey.pem and was just looking to limit which ciphers would be offered. I've found several discussions (here, on stackoverflow, etc.) that mention this error, but those discussions concerned these latter TLS attributes (which I had no problem adding) and not the olcTLSCipherSuite attribute. They also pointed to file permissions being the issue for the certificate files, which I've confirmed is not an issue. I would be grateful if anyone could point me in the right direction Ben

2 2

LDAP proxy backend does not drop idle connections
by Tero Saarni 02 Dec '20

02 Dec '20

Hi, I understood from slapd-ldap(5) description of "idle-timeout" that cached connections towards remote LDAP server would be automatically dropped after <time> seconds. Problem: cached connections that are idle do not get dropped. Questions: (1) Is this expected? (2) Are idle connections kept due to limitation in the implementation: when connection is idle, back-ldap does not have a trigger that could be used to drop idle connections? Background: While experimenting with this, it seems that idle timeout is only checked when there is new activity towards the cached connection i.e. connection needs to become active before idle timeout is checked. If the connection just remains idle, nothing will happen. I'm trying to study the timeout handling in back-ldap code, and I believe I found relevant code at the end of ldap_back_getconn() in bind.c. It will eventually trigger unbind and disconnect, but only when new activity happens after the idle period is reached. I did not find other paths that could trigger unbind of cached connection. -- Tero

4 8

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openldap-technical December 2020