openldap-technical

openldap-technical@openldap.org

15 participants
9797 discussions

username syntax for bind/auth
by Jeff Lebo 21 Oct '14

21 Oct '14

So I've got everything working with my OpenLDAP passthrough to AD... one last thing (I think). Is there a way to make OpenLDAP accept username(a)domain.com instead of the full DN?

2 2

LDAP Replica TLS problem
by Elmopi, Stefano 21 Oct '14

21 Oct '14

Hi, I'm having trouble to run the replica LDAP with TLS, without TLS, all works !! Provider and Consumer are identical CentOS release 6.5 rpm -qa | grep ldap openldap-clients-2.4.23-34.el6_5.1.x86_64 openldap-2.4.23-34.el6_5.1.x86_64 apr-util-ldap-1.3.9-3.el6_0.1.x86_64 nss-pam-ldapd-0.7.5-18.2.el6_4.x86_64 mod_authz_ldap-0.26-16.el6.x86_64 pam_ldap-185-11.el6.x86_64 openldap-servers-2.4.23-34.el6_5.1.x86_64 Provider config, file cn\=config.ldif olcTLSCACertificateFile: /etc/openldap/certs/ldapscert.pem olcTLSCertificateFile: /etc/openldap/certs/ldapscert.pem olcTLSCertificateKeyFile: /etc/openldap/certs/keys/ldapskey.pem olcTLSCipherSuite: TLSv1+RSA:!EXPORT:!NULL olcTLSVerifyClient: never Consumer config: olcSyncrepl: {0}rid=000 provider=ldap://ldpsoc01devpom.sociale.it starttls=yes type=refreshonly retry="5 5 300 +" searchbase="dc=example,dc=it" attrs="*,+" bindmethod=simple binddn="uid=xxxxxxxx,ou=admin_bind,ou=Utenze_Amministratori,dc=example,dc=it" credentials=xxxxxxx interval=60 and, in /etc/openldap/ldap.conf TLS_CACERT /etc/openldap/certs/ldapscert.pem TLS_REQCERT never the certificate is self-signed On the slave, if I try the following command: ldapsearch -ZZ -x -H ldap://ldpsoc01devpom -D 'uid=xxxxxxx,ou=admin_bind,ou=Utenze_Amministratori,dc=example,dc=it' -W 'objectclass=*' -v everything is ok but when I try to use TLS in replication, the process goes wrong. In the Provider log: connection_get(16) connection_get(16): got connid=1030 connection_read(16): checking for input on id=1030 connection_read(16): TLS accept failure error=-1 id=1030, closing connection_closing: readying conn=1030 sd=16 for close connection_close: conn=1030 sd=16 daemon: activity on 1 descriptor daemon: activity on: In the Consumer log: slapd[6508]: =>do_syncrepl rid=000 slap_client_connect: URI=ldap://ldpsoc01devpom.sociale.it Warning, ldap_start_tls failed (-11) slap_client_connect: URI=ldap://ldpsoc01devpom.sociale.it DN="uid=bind_replica,ou=admin_bind,ou=utenze_amministratori,dc=sociale,dc=it" ldap_sasl_bind_s failed (-1) do_syncrepl: rid=000 rc -1 retrying (3 retries left) daemon: activity on 1 descriptor daemon: activity on: Help, I do not know where to turn !!!! Thanks Ing. Stefano Elmopi Cooperativa Capodarco - Resp. Area ICT Gestione Esercizio Via Ostiense 131/L Corpo B, 00154 Roma cell. 3466147165 tel. 0657060500 email:stefano.elmopi@sociale.it -- "Ai sensi e per gli effetti della legge sulla tutela dei dati personali (D.lgs 196/2003), le informazioni contenute nella presente @mail sono di natura riservata e destinate ad un uso aziendale-lavorativo con esclusione di utilizzi ad uso personale; come tali, pertanto, sono riservate esclusivamente ai destinatari sopra indicati. E' proibito leggere, copiare, usare o diffondere il contenuto della presente @mail senza autorizzazione. Se avete ricevuto questa @mail per errore, siete pregati di rispedire la stessa al mittente. Grazie"

4 4

POODLE SSLv3 downgrade attack
by Howard Chu 21 Oct '14

21 Oct '14

You've probably all heard about this "new" attack several times by now. Just to confirm what's already been stated - this attack only affects HTTP browsers that deliberately break the TLS handshake protocol to allow using older SSL versions. It does not affect LDAP software at all. Also, since version 2.4.14 (released February 2009), OpenLDAP has supported TLSProtocolMin slapd config and LDAP_TLS_PROTOCOL_MIN client config directives for selecting the minimum version of SSL/TLS to allow. As this feature has been available for over 5 years there is no reason for any OpenLDAP deployments to be using SSLv3 today. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

6 8

bdb_equality_candidates: (cn) not indexed
by Gremaud Cyrill 21 Oct '14

21 Oct '14

HI list ! I just have a 3-way multi-master replication with openldap for cn=config and HDB. Sometime in the log, I have this error/warning : <= bdb_equality_candidates: (cn) not indexed How can I fix it ? just add olcDbIndex cn eq ??? and my second question is why this warning occurs ? thanks a lot for your response. cyrill gremaud

2 2

Problem with chain overlay
by Elmopi, Stefano 20 Oct '14

20 Oct '14

Hi, I have a problem with the configuration of the Chain Overlay. Provider and Consumer are identical CentOS release 6.5 rpm -qa | grep ldap openldap-clients-2.4.23-34.el6_5.1.x86_64 openldap-2.4.23-34.el6_5.1.x86_64 apr-util-ldap-1.3.9-3.el6_0.1.x86_64 nss-pam-ldapd-0.7.5-18.2.el6_4.x86_64 mod_authz_ldap-0.26-16.el6.x86_64 pam_ldap-185-11.el6.x86_64 openldap-servers-2.4.23-34.el6_5.1.x86_64 On the Consumer I imported the ldif file: dn: olcOverlay=chain,olcDatabase={-1}frontend,cn=config objectClass: olcOverlayConfig objectClass: olcChainConfig olcOverlay: chain olcChainCacheURI: FALSE olcChainMaxReferralDepth: 1 olcChainReturnError: FALSE and I created the file. /etc/openldap/slapd.d/cn=config/olcDatabase={-1}frontend/olcOverlay={1}chain.ldif and after that I can not understand what I do. I've read a few things on the internet but have not been able to arrive at a solution, I tried to import the ldif file: dn: olcDatabase=ldap,olcOverlay={1}chain,olcDatabase={-1}frontend,cn=config objectClass: olcLDAPConfig objectClass: olcChainDatabase olcDatabase: ldap olcDbURI: "ldap://ldpsoc01devpom.sociale.it" olcDbIDAssertBind: mode=self flags=prescriptive,proxy-authz-non-critical bindmethod=simple timeout=0 network-timeout=0 binddn="uid=pippo,ou=admin_esercizio,ou=Utenze_Amministratori,dc=sociale,dc=it" credentials="*******" keepalive=0:0:0 olcDbIDAssertAuthzFrom: * olcDbRebindAsUser: FALSE olcDbChaseReferrals: TRUE olcDbTFSupport: no olcDbProxyWhoAmI: FALSE olcDbProtocolVersion: 3 olcDbSingleConn: FALSE olcDbCancel: abandon olcDbUseTemporaryConn: FALSE olcDbConnectionPoolMax: 16 olcDbNoRefs: FALSE olcDbNoUndefFilter: FALSE but what I try to import it, I get the following error ldapadd -d 5 -H ldap://localhost:389 -x -W -D "cn=admin,cn=config" -f chaing_entry.ldif res_errno: 32, res_error: <>, res_matched: <olcDatabase={-1}frontend,cn=config> ldap_free_request (origid 2, msgid 2) ldap_parse_result ber_scanf fmt ({iAA) ber: ber_scanf fmt (}) ber: ldap_msgfree ldap_err2string ldap_add: No such object (32) matched DN: olcDatabase={-1}frontend,cn=config ldap_free_connection 1 1 ldap_send_unbind ber_flush2: 7 bytes to sd 4 ldap_free_connection: actually freed I do not know what to do !!!! My problem is that I use the Consumer ldap for authentication of some applications and if a user fails for more than 5 times the password, it should be blocked but being Consumer ldap read-only, the locking is not done !!! HELP !!! Ing. Stefano Elmopi Cooperativa Capodarco - Resp. Area ICT Gestione Esercizio Via Ostiense 131/L Corpo B, 00154 Roma cell. 3466147165 tel. 0657060500 email:stefano.elmopi@sociale.it -- "Ai sensi e per gli effetti della legge sulla tutela dei dati personali (D.lgs 196/2003), le informazioni contenute nella presente @mail sono di natura riservata e destinate ad un uso aziendale-lavorativo con esclusione di utilizzi ad uso personale; come tali, pertanto, sono riservate esclusivamente ai destinatari sopra indicati. E' proibito leggere, copiare, usare o diffondere il contenuto della presente @mail senza autorizzazione. Se avete ricevuto questa @mail per errore, siete pregati di rispedire la stessa al mittente. Grazie"

4 3

Seems that syncprov holds up LMDB's reclaiming while handle a syncrepl requests.
by Леонид Юрьев 20 Oct '14

20 Oct '14

Under heavy load conditions with syncrepl a lot of FreeDB records is generated, without any other reading activity. Is really a lot, up to 90% of DB space, a sample is below. I assume that the bugfix of ITS#7904 does not affected for syncprov overlay and syncrepl. http://www.openldap.org/its/index.cgi/Software%20Bugs?id=7904 Which is the best way to verify this and fix? Could anybody pointed me to a code? Leonid. --- Environment Info Map address: (nil) Map size: 2000000000 Page size: 4096 Max pages: 488281 Number of pages used: 480301 Last transaction ID: 1485433 Tail transaction ID: 1485433 Max readers: 126 Number of readers used: 0 Freelist Status Tree depth: 3 Branch pages: 8 Leaf pages: 1121 Overflow pages: 1 Entries: 28991 Page Allocation Info Max pages: 488281 100% Number of pages used: 480301 98.4% Remained: 7980 1.6% Used now: 33397 6.8% Free pages: 446904 91.5% Reading: 9 0.0% Reclaimable: 446895 91.5% Available: 454875 93.2% Status of Main DB Tree depth: 1 Branch pages: 0 Leaf pages: 1 Overflow pages: 0 Entries: 6

2 1

Segmentation fault in s23_clnt.c when used in a library
by Tobias Ljunggren 20 Oct '14

20 Oct '14

Hello, I've been trying to track a segmentation fault for a couple of days but I'm running out of ideas and need some help or suggestion on how to proceed. Perhaps this is the wrong forum and if so I apologize. It's also worth mentioning that I don't have any knowledge about the openSSL library source code but I've been working with ldap libraries for quite some time (about 10 years). What I have is shared object (.so) that is loaded from another program (nothing I have control of) using a public API. My library loads openLDAP (libldap_r and liblber) using dlopen/dlsym. After some initialization code I try to bind to a ldap source (ldaps://ldaphost:636) but I get a segmentation fault in s23_clnt.c at line 159: else if (s->ctx->info_callback != NULL) For some reason s->ctx is a null pointer. My first thoughts was that I do something I shouldn't prior to ldap_sasl_bind_s which corrupts the LDAP handle but after days with gdb and valgrind I still can't find anything. openLDAP version used is 2.4.40 built with openSSL 1.0.1i. If I copy the ldap code to a test executable it works fine. Is there anything special to consider when loading the libraries from a shared object? I understand that it is almost impossible to give me any good answers but since I'm a bit frustrated I hope someone can give me some hints. Best regards, Tobias

2 4

Proper way to de initialize library
by Tobias Ljunggren 19 Oct '14

19 Oct '14

Hello, What is the proper way to de-initialize openLDAP library? Let's assume I have ldap_initialize (ldaps://....) a couple of general ldap_set_option some ldap_set_option for TLS ldap_sasl_bind_s Is ldap_unbind_s all that's required? My problem is that if I do it this way when using openLDAP from a shared object and the process unloads the shared object and then loads it again (restarts my library) TLS won't work anymore. Probably there is one or more global variables in openLDAP that needs to be reset before unload to make sure the initialization works. I looked at the ldapsearch example provided, in common.c, and noticed a call to ldap_pvt_tls_destroy. I tried that but it doesn't make any difference. I've compiled openLDAP to use Mozilla NSS. Best regards, Tobias

2 2

[LMDB] some few questions
by Klaus Malorny 17 Oct '14

17 Oct '14

Hi, LMDB seems to be quite the right database I am looking for in order to speed up my application. However, I still need to figure some things out. While I could get many answers to my questions by skimming through the archive, the following things are still unclear to me, and it would be quite nice if someone could clarify them: - in the documentation, I saw two limits: the key is limited to 511 bytes (by default) and the data is limited to 16777215 bytes. Is this correct? For larger data sizes, is the data still maintained in one contiguous block, so that the application can still access it directly without any need of copying within LMDB? Or it is better to split larger data into multiple key/value pairs? - I discovered the return code "MDB_TXN_FULL". By what means are transactions limited? I might consider to use few, but quite large transactions dealing with hundreds of thousands key/value pairs to be created, updated or deleted in some circumstances. - I saw the discussion about the predefined database size, and that it is recommended to use a never-to-be-reached size and to rely on the sparse file capabilities of the underlying OS. If I would not want to go this way: Is it correct that if I encounter an "MDB_MAP_FULL" return code, it would be sufficient to abort the current transaction, resize the database using mdp_env_set_mapsize and repeat the transaction? Thanks in advance and regards, Klaus

2 3

AW: Q: accesslog and sessions
by Uwe Werler 17 Oct '14

17 Oct '14

-----Ursprüngliche Nachricht----- Von: Ulrich Windl <Ulrich.Windl(a)rz.uni-regensburg.de> Gesendet: Do 16.10.2014 13:46 Betreff: Q: accesslog and sessions An: openldap-technical(a)openldap.org; > Hi! > > I have configured accesslog for modification (attempts) in a multi-master > configuration. Comparing accesslogs after some changes, I find some issues > (openLDAP 2.4.26 of SLES11 SP3): > > On the originating server the "reqSession" varies with the connection made, > while on a replication consumer the "reqSession" seems fixed (always 2 in one > case). 'cause of replication. > Also on the originating server I see the authenticated DN in > "reqAuthzID", while on the replication consumer it seems to be always > "cn=Admin,dc=example,dc=org". "reqStart" and "reqEnd" are also local for the > LDAP server. 'cause the repl consumer writes to the database as admin user. > > Now at least I have a problem with "reqSession": If you examine accesslog at > some later time, those volatile session IDs don't tell you anything anymore > (e.g. the host that opened the connection). Could acesslog be modified to add > some details from the session (like monitorConnectionPeerAddress, > monitorConnectionStartTime)? > > Regards, > Ulrich Windl > This woule be a very nice feature, indeed. > >

4 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openldap-technical