openldap-technical

openldap-technical@openldap.org

9 participants
9867 discussions

Re: On removing a duplicated ppolicy overlay
by Daniel Howard 28 Nov '18

28 Nov '18

On Tue, Nov 27, 2018 at 3:17 PM Quanah Gibson-Mount <quanah(a)symas.com> wrote: > --On Tuesday, November 27, 2018 2:22 PM -0800 Daniel Howard > <dannyman(a)toldme.com> wrote: > > > I had been yearning for a config file, and it turns out I had them all > > along! > > It's a database, not configuration files. Removing files from underneath > a > database is generally not a good idea, although YMMV. > > > I am sharing my experience here, for the next person who finds themselves > > googling around, trying to figure out how to remove or tweak a config in > > OpenLDAP. It is nowhere near as complicated as what I had read. > > This is the wrong advice. It is also fairly trivial to do what you > avoided. > > a) slapcat -n 0 -l /tmp/config.ldif > b) Remove the duplicate entries from /tmp/config.ldif > c) mv /path/to/current/config /path/to/current/config.old;mkdir -p > /path/to/current/config > d) slapadd -n 0 -l /tmp/config.ldif > I can see how a naive sysadmin might interpret the various text files in /etc/ldap/slapd.d/cn=config/ as configuration files ... that could be carefully edited by hand ... or managed programatically through the local configuration management system. I appreciate your admonition that this interpretation is wrong, and that these would-be "config" files in the system configuration file hierarchy are in fact a software-managed database, so we should not edit what appear to be plain text configuration files, but simply export them to a text file, carefully edit the export of the database, delete the entire config file hierarchy, and then reimport the database. If I may make a minor feature suggestion: whenever I get a file into /etc that needs a special workflow, I like to put warnings in the comments at the top of such files, advising that the file(s) shouldn't be edited by hand, and explaining the proper workflow. (The visudo command is a golden standard in this regard.) djh@djh-p5510 ~> sudo head -3 /etc/sudoers # # This file MUST be edited with the 'visudo' command as root. # Perhaps this is a consideration that is already on the roadmap? Thanks, -danny -- http://dannyman.toldme.com

3 2

On removing a duplicated ppolicy overlay
by Daniel Howard 28 Nov '18

28 Nov '18

Hello, Back in April or May, I was trying to add and tweak a password policy, invoking a command like this multiple times: sudo ldapmodify -Q -Y EXTERNAL -H ldapi:/// -a -f ppolicy-overlay.ldif This created multiple password policy overlays, and the LDAP server started to crash with some frequency. Of course, you can not use this interface to DELETE a policy overlay, so I went about researching "hot to remove a ppolicy overlay" and go into some complicated process where you have to export the database, remove olc* entries, delete your database and re-import. My attention shifted to other priorities. Yesterday, I turned back to the question of how to remove the duplicated ppolicy overlays and started exporting the database, but I couldn't find the ppolicy stuff in my slapcat output. Another trip to the search mines and I discovered this gem: https://serverfault.com/a/280836/72839 While you are asked to configure stuff using an LDAP command that cannot delete duplicate policy overlays, the config data doesn't get written into the database, but just placed in plain-text files in a directory structure. Removing duplicated overlays is as simple as stop slapd, remove the files, start slapd. Similarly, you could tweak your ppolicy overlay or possibly even bootstrap new servers by merely editing the right config files in the right place. I had been yearning for a config file, and it turns out I had them all along! I am sharing my experience here, for the next person who finds themselves googling around, trying to figure out how to remove or tweak a config in OpenLDAP. It is nowhere near as complicated as what I had read. Thanks, -danny -- http://dannyman.toldme.com

2 1

openldap stopped authenticating
by Lang, Adam 27 Nov '18

27 Nov '18

Hello, I woke up to an issue today where SSH access to our servers no longer works due to issues with LDAP authentication. Oddly, ldapsearch with admin credentials interacts with the LDAP server fine. If I check for ldapusers using getent passwd, none are returned. The slapd auditlog records the failed attempts. When trying to su as an ldap user, it returns "no passwd entry". Nothing "should" have changed over night, so any ideas of where to look will be appreciated. Adam The information contained in or attached to this e-mail is intended only for the use of the addressee. If you are not the intended recipient of this e-mail, or a person responsible for delivering it to the intended recipient, you are strictly prohibited from disclosing, copying, distributing, or retaining this e-mail or any part of it. It may contain information which is confidential and/or covered by legal, professional or other privilege under applicable law. If you have received this e-mail in error, please notify the author by replying to this e-mail immediately and delete this e-mail from your system. The views expressed in this email may not necessary be the views held by the organization. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.

2 2

Empty search result
by Fabiano Sidler 27 Nov '18

27 Nov '18

Hello! What can be the cause for ldapsearch without filter returning everything as expected, but adding a filter (which works well against a 389 and an AD installation) just returns nothing? I can provide configs and logs if this is normal but unexpected (by me) behaviour. Greetings, Fabiano

3 2

SSL_library_init in -lssl... no, configure: error: Could not locate TLS/SSL package
by Synthea 27 Nov '18

27 Nov '18

While I try to configure openldap 2.4.44 I get this error: checking openssl/ssl.h usability... yes checking openssl/ssl.h presence... yes checking for openssl/ssl.h... yes checking for SSL_library_init in -lssl... no checking for ssl3_accept in -lssl... no configure: error: Could not locate TLS/SSL package ssl.h is in /usr/include/openssl/ssl.h and the version of openssl library is 1.1.0f-3

2 1

Q: meaning of ACL "disclose" access
by Ulrich Windl 26 Nov '18

26 Nov '18

Hi! The manual page slapd.access explains: "The disclose access level allows disclosure of information on error." I don't quite understand what this is saying: Can the requester find out a specific object or attribute exists without actually reading its value? Regards, Ulrich

2 1

N-Way MMR between local LDAP and Cloud LDAP
by Alan Lukens 26 Nov '18

26 Nov '18

I have been asked to look into adding an LDAP instance in AWS Cloud environment. This LDAP instance would participate in our current N-Way MMR that we have locally. Does anyone have any recommendations, experience, or insight into attempting something like this? Any help would be appreciated. Alan Lukens Identity Management Specialist University of Massachusetts Amherst, IT NSS

1 0

ldapmodify add olcSyncrepl (okey but not okey)
by lejeczek 19 Nov '18

19 Nov '18

hi everyone I'm must be doing something trivially wrong and am hoping someone could help. I'm trying to add second replica: $ ldapmodify -vv -h rider.my.dom:1389 -D "cn=admin,cn=config" -w my.Biotec13 -x ldap_initialize( ldap://rider.my.dom:1389 ) dn: olcDatabase={1}bdb,cn=config changetype: modify add: olcSyncrepl: rid=002 provider=ldap://swir.my.dom:1389 bindmethod=simple timeout=0 network-timeout=0 binddn="uid=replicator,ou=people,dc=my,dc=dom" credentials="lejek9090" keepalive=0:0:0 starttls=no filter="(objectclass=*)" searchbase="dc=my,dc=dom" scope=sub attrs="*,+" schemachecking=off type=refreshOnly interval=00:00:10:00 retry="5 5 300 +" exit code of the above to shell is 0 yet next ldapsearch finds no such new entry exists. At the time of ldapmodify in logs I see: Nov 19 14:40:48 rider slapd[90048]: slap_queue_csn: queueing 0x7f22cc111e00 20181119144048.167126Z#000000#005#000000 Nov 19 14:40:48 rider slapd[90048]: slap_graduate_commit_csn: removing 0x7f22cc111e00 20181119144048.167126Z#000000#005#000000 How to get it work? Many thanks, L.

4 3

Re: syncrepl schema error
by aRaviNd 19 Nov '18

19 Nov '18

HI Quanah, Yes, there was duplicate values in DIT which was causing slaves to not sync the data. Thanks for your guidance Regards, Aravind M D On Sun, Nov 18, 2018 at 3:35 AM Quanah Gibson-Mount <quanah(a)symas.com> wrote: > --On Saturday, November 17, 2018 9:38 PM +0530 aRaviNd > <ambadiaravind(a)gmail.com> wrote: > > > If remove the schema changes replication works fine. Could you please let > > us know whats going wrong with the configuration? > > Most likely, you have two values in the attribute that are different when > case sensitive, but the same when case insensitive, i.e.: > > memberUID: AbcD > memberUID: aBCd > > Before your schema change, these are considered different. AAfter your > schema change, they are the same. So when a modification occurs to the > attribute they are now seen as duplicate values and it breaks replication. > > --Quanah > > > > -- > > Quanah Gibson-Mount > Product Architect > Symas Corporation > Packaged, certified, and supported LDAP solutions powered by OpenLDAP: > <http://www.symas.com> > >

1 0

delete a user schema from cn=config
by Derek Zhou 19 Nov '18

19 Nov '18

Hi list, I was experimenting locally written schema with a recent build of slapd. I added the schema ldif with no problem using ldapadd -QY EXTERNAL -H ldapi:/// ... But then I realized I made a mistake, so I try to delete it with ldapdelete -QY EXTERNAL -H ldapi:/// it says: ldap_delete: Server is unwilling to perform (53) what does it mean? The schema is not used by any data on the server. I can use slapmodify to remove it after server shutdown, but that kind of suck and not much different, or even worse than editing conf file? Derek

4 8

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openldap-technical