openldap-technical May 2012

openldap-technical@openldap.org

76 participants
101 discussions

Multi-Master Replication
by Brian Carpio 30 May '12

30 May '12

Hi, I'm currently using Ubuntu 10.04 (I've set this up on RHEL 5.x but the config is way different in Ubuntu). Anyway, at first I figured I had everything working. When I made an update to ldap01 I immediately saw the change on ldap02. However, if I take down slapd on ldap02 (or 01) and I add LDAP entries into ldap01, then bring ldap02's slapd process back online I never see the entries created while slapd was down on ldap02. New entries continue to propigate between ldap01 and ldap02 and long as both servers have the slapd process running, but the entries created when slapd was down on ldap02 never propagate to 02. Here are my configs and ldap versions: ii slapd 2.4.21-0ubuntu5.7 OpenLDAP server (slapd) ---- /etc/ldap/slapd.d/cn=config/olcDatabase={0}config.ldif ----- # AUTO-GENERATED FILE - DO NOT EDIT!! Use ldapmodify. # CRC32 deacdc79 dn: olcDatabase={0}config objectClass: olcDatabaseConfig olcDatabase: {0}config olcAccess: {0}to * by dn.exact=gidNumber=0+uidNumber=0,cn=peercred,cn=external ,cn=auth manage by * break olcAccess: {1}to attrs=userPassword,shadowLastChange by self write by anonymou s auth by dn="cn=admin,dc=example,dc=net" write by * none olcAccess: {2}to * by self write by dn="cn=admin,dc=example,dc=net" write b y * read structuralObjectClass: olcDatabaseConfig entryUUID: 19eb3cc6-3898-1031-954c-351a2fbb42e9 creatorsName: cn=config createTimestamp: 20120522202605Z olcSyncrepl: {0}rid=001 provider="ldap://ldap-01:389" type=refreshAndPer sist retry="5 5 300 +" searchbase="cn=config" attrs="*,+" bindmethod=simple b inddn="cn=admin,dc=example,dc=net" credentials="secret" olcSyncrepl: {1}rid=002 provider="ldap://arch-ldap-02:389" type=refreshAndPer sist retry="5 5 300 +" searchbase="cn=config" attrs="*,+" bindmethod=simple b inddn="cn=admin,dc=example,dc=net" credentials="secret" olcMirrorMode: TRUE entryCSN: 20120528195647.027315Z#000000#000#000000 modifiersName: cn=admin,dc=example,dc=net modifyTimestamp: 20120528195647Z ---- /etc/ldap/slapd.d/cn=config/olcDatabase={0}config/olcOverlay={0}syncprov.ldif ---- # AUTO-GENERATED FILE - DO NOT EDIT!! Use ldapmodify. # CRC32 807029fa dn: olcOverlay={0}syncprov objectClass: olcOverlayConfig objectClass: olcSyncProvConfig olcOverlay: {0}syncprov olcSpNoPresent: TRUE structuralObjectClass: olcSyncProvConfig entryUUID: 3be00cb6-3dee-1031-8f60-519aa1b6f74f creatorsName: cn=admin,dc=example,dc=net createTimestamp: 20120529152514Z entryCSN: 20120529152514.987191Z#000000#000#000000 modifiersName: cn=admin,dc=example,dc=net modifyTimestamp: 20120529152514Z ---- /etc/ldap/slapd.d/cn=config/olcDatabase={1}hdb.ldif ---- # AUTO-GENERATED FILE - DO NOT EDIT!! Use ldapmodify. # CRC32 1b0a3130 dn: olcDatabase={1}hdb objectClass: olcDatabaseConfig objectClass: olcHdbConfig olcDatabase: {1}hdb olcDbDirectory: /var/lib/ldap olcSuffix: dc=example,dc=net olcAccess: {0}to attrs=userPassword,shadowLastChange by self write by anonymou s auth by dn="cn=admin,dc=example,dc=net" write by * none olcAccess: {1}to dn.base="" by * read olcAccess: {2}to * by self write by dn="cn=admin,dc=example,dc=net" write b y * read olcLastMod: TRUE olcRootDN: cn=admin,dc=example,dc=net olcRootPW:: e1NTSEF9Ni9IZWJCczRTbmJQYlc4NHFOMWxHWUI5NVNoVUl4U20= olcDbCheckpoint: 512 30 olcDbConfig: {0}set_cachesize 0 2097152 0 olcDbConfig: {1}set_lk_max_objects 1500 olcDbConfig: {2}set_lk_max_locks 1500 olcDbConfig: {3}set_lk_max_lockers 1500 olcDbIndex: objectClass eq structuralObjectClass: olcHdbConfig entryUUID: 19ebfdc8-3898-1031-9554-351a2fbb42e9 creatorsName: cn=config createTimestamp: 20120522202605Z olcSyncrepl: {0}rid=001 provider="ldap://ldap-01:389" type=refreshAndPer sist retry="5 5 300 +" searchbase="dc=example,dc=net" attrs="*,+" bindmeth od=simple binddn="cn=admin,dc=example,dc=net" credentials="secret" olcSyncrepl: {1}rid=002 provider="ldap://ldap-02:389" type=refreshAndPer sist retry="5 5 300 +" searchbase="dc=example,dc=net" attrs="*,+" bindmeth od=simple binddn="cn=admin,dc=example,dc=net" credentials="secret" olcMirrorMode: TRUE entryCSN: 20120528195647.026244Z#000000#000#000000 modifiersName: cn=admin,dc=example,dc=net modifyTimestamp: 20120528195647Z ----- /etc/ldap/slapd.d/cn=config/olcDatabase={1}hdb/olcOverlay={0}syncprov.ldif ---- # AUTO-GENERATED FILE - DO NOT EDIT!! Use ldapmodify. # CRC32 807029fa dn: olcOverlay={0}syncprov objectClass: olcOverlayConfig objectClass: olcSyncProvConfig olcOverlay: {0}syncprov olcSpNoPresent: TRUE structuralObjectClass: olcSyncProvConfig entryUUID: 3be00cb6-3dee-1031-8f60-519aa1b6f74f creatorsName: cn=admin,dc=example,dc=net createTimestamp: 20120529152514Z entryCSN: 20120529152514.987191Z#000000#000#000000 modifiersName: cn=admin,dc=example,dc=net modifyTimestamp: 20120529152514Z

2 1

Re: OpenLDAP freeze
by Ioan Indreias 29 May '12

29 May '12

Are there any chances to have your feedback on the information provided? Best regards, Ioan On Fri, May 18, 2012 at 11:25 AM, Ioan Indreias <indreias(a)gmail.com> wrote: > Hello all, > > We are running OpenLDAP in a SLAVE-MASTER configuratiorn (Slave for > another OpenLDAP server //L1// and Master for 2 Axigen Back End nodes > //B1 and B2//). > > Currently we have ~31000 accounts and experience random freeze events > of the slapd (nothing writing in the logs, CPU 0%) when a series of > add/delete operations are performed over the normal LDAP > traffic.Random means an interval between 15 and 80 minutes after we > start add/delete accounts. > > The add/delete bash script is running in loop, adding 60 accounts, > sleep 20 sec, delete the accounts and sleep another 40 sec. All > operations are performed on the MASTER L1 server and are propagated > correctly to our server (till is freezing of course). > > Running with 2.4.23 we have considered to upgrade to 2.4.31 but the > same problem was observed. On both cases we have used BDB 4.7.25, with > all available patches. > > The server is a RHEL 5.5, 64 bits with plenty of memory and CPUs. > > I am attaching 3 archives: the slapd configuration and gdb+db_stat for > 2 freeeze events. > > Could somebody point if there is a slapd or bdb problem? Any hints are > appreciated. > > Best regards, > Ioan Indreias > www.modulo.ro > > === > May 18 09:37:10 saevrvmp11 slapd[13834]: @(#) $OpenLDAP: slapd 2.4.31 > (May 10 2012 16:11:06) $ > root@host64.modulo.ro:/root/openldap-2.4.31/servers/slapd > > [root@host tmp]# ldd /usr/sbin/slapd > libuuid.so.1 => /lib64/libuuid.so.1 (0x0000003efe000000) > libssl.so.6 => /lib64/libssl.so.6 (0x0000003f05400000) > libcrypto.so.6 => /lib64/libcrypto.so.6 (0x0000003f00800000) > libresolv.so.2 => /lib64/libresolv.so.2 (0x0000003f01800000) > libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003efb800000) > libc.so.6 => /lib64/libc.so.6 (0x0000003efac00000) > /lib64/ld-linux-x86-64.so.2 (0x0000003efa800000) > libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2 > (0x0000003f02800000) > libkrb5.so.3 => /usr/lib64/libkrb5.so.3 (0x0000003f03000000) > libcom_err.so.2 => /lib64/libcom_err.so.2 (0x0000003f01000000) > libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 (0x0000003f02c00000) > libdl.so.2 => /lib64/libdl.so.2 (0x0000003efb000000) > libz.so.1 => /usr/lib64/libz.so.1 (0x0000003efbc00000) > libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0 > (0x0000003f02400000) > libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x0000003f02000000) > libselinux.so.1 => /lib64/libselinux.so.1 (0x0000003efc400000) > libsepol.so.1 => /lib64/libsepol.so.1 (0x0000003efc000000) > ===

2 7

UPGRADING OPENLDAP
by Borresen, John - 0442 - MITLL 29 May '12

29 May '12

Planning to upgrade our OpenLDAP from 2.4.23 to 2.4.31 shortly and just getting my ducks in a row. 1) my current Berkeley flavor is 4.8.30 2) As stated, OpenLDAP is 2.4.23 (using slapd.d) Looking for any "gotchas" to be on look out for. Can I do the upgrade on top of the current directory structure, restore the config then restart? Am I going to need to upgrade my flavor of Berkeley? I had originally attempted to use Berkeley 5.2.36 but never could get it to build/compile correctly on my platform (too many compilation errors to list). Dave Borresen Solaris/Linux Systems Administrator Surveillance Systems Group MIT Lincoln Laboratory john.borresen(a)ll.mit.edu

2 1

Replication Design Advice
by Andrei Bănaru 29 May '12

29 May '12

Hello OpenLDAP users, I’m looking for some advice concerning an OpenLDAP solution I’m about to deploy between 4 locations in company I work for. Currently I’ve implemented a LDAP DIT in my country and we’ve had exquisite results. I’ve integrated RADIUS for wireless authentication, MIT Kerberos, Samba PDC, dovecot and the list can continue but that’s not the scope of this message. We have some global services located in one of the countries that all other 3 countries use ( trac, svn, web2project, alfresco ). We want that each country to have it’s own LDAP DIT ( we don’t want to have a global LDAP with slaves in each country because some of us want locally significant objects ( for authorization purposes ) and having a slave LDAP means read-only ). That’s why I thought of using multi-n-master on each of the four LDAP servers. The ideea I had was that each country will have only a portion of the DIT being sent to the others ( we narrow the searchbase in syncrepl ): Country 1 sends ou=COUNTRY-1,dc=example,dc=com Country 2 sends ou=COUNTRY-2,dc=example,dc=com Country 3 sends ou=COUNTRY-3,dc=example,dc=com Country 4 sends ou=COUNTRY-4,dc=example,dc=com In each ou=COUNTRY-{1..4} they will have ou=People and ou=Groups. Basically that’s the only thing I want to be consistent across all LDAP DITs. I’ve tested the solution using some virtual machines and besides the starttls and some things each administrator will have to be cautious about things went smoothly. I've also read something about slapo-translucent - will now test to see how it works. Can I get some suggestions / maybe a whole new architecture for my needs in case I didn’t foresee problems ? Thx! -- Andrei BĂNARU Internal Support CCNA Security, CCIP StreamWIDE Romania

1 0

How do tool verify certs with ldapi:// ?
by Peter Marschall 28 May '12

28 May '12

Hi, how do the openldap tools technically verfify certificates with ldapi:// ? With ldapi, you don't have a hostname or IP address, so how do the openldap tools do it? I tried to browse the code but got losat somewhere ion the way. Any hints to the code or a short step-by-step explanation will help. Background of this question: I want to implement the feature in perl-ldap. Thanks in advance for your help Peter -- Peter Marschall peter(a)adpm.de

3 13

Re: how can make slave use tls to connect to master for syncrepl (solved)
by zhong ming wu 28 May '12

28 May '12

Never mind. I had to put this line in the sysrepl section of the slave starttls=yes Sorry about the noise. On Sun, May 27, 2012 at 10:29 PM, zhong ming wu <mr.z.m.wu(a)gmail.com> wrote: > Hello > > I am using version 2.4 and in the process of setting up a master/slave > pair using syncrepl. > > This is working as expected if I don't have enforce security and > confidentiality with "security ssf=128" global directive in the > master. > As soon as I turn it on, replication stops working. > > It seems that the slave consumer is not using TLS to connect to > master. However I can use 'ldapsearch' with '-ZZ' option to connect > to master from slave and get all records I want. > > On my slave machine, I also have the following directive > > TLS_CACERT /etc/pki/tls/certs/ca.crt.crl > > in ldap.conf > > Notice that without this line 'ldapXXX' commands with '-ZZ' fails from > slave to master. This confirms that at least 'ldap.conf' is in the > correct location at least as far as 'ldapXXX' commands are concerned. > > Can someone point me in the right direction? I have read many > chapters on this page > > http://www.openldap.org/doc/admin24/index.html > > Both slave and master are on centos 6.2 and openldap software is > standard centos rpm. > > Here are the log entries on the master when slave fails to bind with TLS > > May 27 22:14:53 cat slapd[2456]: conn=1000 fd=13 ACCEPT from > IP=192.168.0.2:41083 (IP=0.0.0.0:389) > May 27 22:14:53 cat slapd[2456]: conn=1000 op=0 BIND > dn="cn=root,dc=example,dc=com" method=128 > May 27 22:14:53 cat slapd[2456]: conn=1000 op=0 RESULT tag=97 err=13 > text=confidentiality required > May 27 22:14:53 cat slapd[2456]: conn=1000 op=1 UNBIND > May 27 22:14:53 cat slapd[2456]: conn=1000 fd=13 closed > > Sincerely > > Mr Wu

1 0

OpenLDAP proxy to Active Directory
by Jonathan van der Wat 28 May '12

28 May '12

Greetings, I'm new to OpenLDAP and am trying to implement the following: User authentication (PAM + SSSD) on CentOS Linux servers via OpenLDAP proxy to Active Directory. I am able to perform the following search from the OpenLDAP proxy without any apparent issues: * [root@openldap ~]# ldapsearch -x -h /mydomaincontroller/ -LLL -b dc=msad,dc=inet,dc=com -D cn=ldap,cn=users,dc=msad,dc=inet,dc=com -W '(sAMAccountName=jonathanv)' cn sAMAccountName Enter LDAP Password: dn: CN=jonathan,CN=Users,DC=msad,DC=inet,DC=com cn: jonathan sAMAccountName: jonathanv # refldap://ForestDnsZones.msad.inet.com/DC=ForestDnsZones,DC=msad,DC=inet,DC… # refldap://DomainDnsZones.msad.inet.com/DC=DomainDnsZones,DC=msad,DC=inet,DC… # refldap://msad.inet.com/CN=Configuration,DC=msad,DC=inet,DC=com* However, when asking the OpenLDAP proxy: *[root@openldap ~]# ldapsearch -x -h /localhost/ -LLL -b dc=msad,dc=inet,dc=com -D cn=ldap,cn=users,dc=msad,dc=inet,dc=com -W '(sAMAccountName=jonathanv)' cn sAMAccountName Enter LDAP Password: # refldap://ForestDnsZones.msad.inet.com/DC=ForestDnsZones,DC=msad,DC=inet,DC… # refldap://DomainDnsZones.msad.inet.com/DC=DomainDnsZones,DC=msad,DC=inet,DC… # refldap://msad.inet.com/CN=Configuration,DC=msad,DC=inet,DC=com* Also, I've configured my CentOS server's using SSSD. When trying to authenticate as user jonathanv, I receive a message that user jonathanv is not found. I am using OpenLDAP server version 2.4.23-20. I am starting the OpenLDAP from the command line as follows: *slapd -f -d 2 -f /etc/openldap/slapd.conf -g ldap -h ldap:/// -l LOCAL4 -u ldap -n slapd-ldap* Here is the output of my slapd.conf file: *# # See slapd.conf(5) for details on configuration options. # This file should NOT be world readable. # include /etc/openldap/schema/corba.schema include /etc/openldap/schema/core.schema include /etc/openldap/schema/cosine.schema include /etc/openldap/schema/duaconf.schema include /etc/openldap/schema/dyngroup.schema include /etc/openldap/schema/inetorgperson.schema include /etc/openldap/schema/java.schema include /etc/openldap/schema/misc.schema include /etc/openldap/schema/nis.schema include /etc/openldap/schema/openldap.schema include /etc/openldap/schema/ppolicy.schema include /etc/openldap/schema/collective.schema # Allow LDAPv2 client connections. This is NOT the default. allow bind_v2 # Do not enable referrals until AFTER you have a working directory # service AND an understanding of referrals. #referral ldap://root.openldap.org pidfile /var/run/openldap/slapd.pid argsfile /var/run/openldap/slapd.args # Load dynamic backend modules # - modulepath is architecture dependent value (32/64-bit system) # - back_sql.la overlay requires openldap-server-sql package # - dyngroup.la and dynlist.la cannot be used at the same time # modulepath /usr/lib/openldap # modulepath /usr/lib64/openldap # moduleload accesslog.la # moduleload auditlog.la # moduleload back_sql.la # moduleload chain.la # moduleload collect.la # moduleload constraint.la # moduleload dds.la # moduleload deref.la # moduleload dyngroup.la # moduleload dynlist.la # moduleload memberof.la # moduleload pbind.la # moduleload pcache.la # moduleload ppolicy.la # moduleload refint.la # moduleload retcode.la moduleload rwm.la # moduleload seqmod.la # moduleload smbk5pwd.la # moduleload sssvlv.la # moduleload syncprov.la # moduleload translucent.la # moduleload unique.la # moduleload valsort.la # The next three lines allow use of TLS for encrypting connections using a # dummy test certificate which you can generate by changing to # /etc/pki/tls/certs, running "make slapd.pem", and fixing permissions on # slapd.pem so that the ldap user or group can read it. Your client software # may balk at self-signed certificates, however. # TLSCACertificateFile /etc/pki/tls/certs/ca-bundle.crt # TLSCertificateFile /etc/pki/tls/certs/slapd.pem # TLSCertificateKeyFile /etc/pki/tls/certs/slapd.pem # Sample security restrictions # Require integrity protection (prevent hijacking) # Require 112-bit (3DES or better) encryption for updates # Require 63-bit encryption for simple bind # security ssf=1 update_ssf=112 simple_bind=64 # Sample access control policy: # Root DSE: allow anyone to read it # Subschema (sub)entry DSE: allow anyone to read it # Other DSEs: # Allow self write access # Allow authenticated users read access # Allow anonymous users to authenticate # Directives needed to implement policy: # access to dn.base="" by * read # access to dn.base="cn=Subschema" by * read # access to * # by self write # by users read # by anonymous auth # # if no access controls are present, the default policy # allows anyone and everyone to read anything but restricts # updates to rootdn. (e.g., "access to * by * read") # # rootdn can always read and write EVERYTHING! # enable on-the-fly configuration (cn=config) database config access to * by dn.exact="gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth" manage by * none # enable server status monitoring (cn=monitor) database monitor access to * by dn.exact="gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth" read by dn.exact="cn=Manager,dc=my-domain,dc=com" read by * none ####################################################################### # database definitions ####################################################################### database bdb suffix "dc=inet,dc=local" checkpoint 1024 15 rootdn "cn=Manager,dc=inet,dc=local" rootpw xxxxxxxxxxxxxxxx # Cleartext passwords, especially for the rootdn, should # be avoided. See slappasswd(8) and slapd.conf(5) for details. # Use of strong authentication encouraged. # rootpw secret # rootpw {crypt}ijFYNcSNctBYg # The database directory MUST exist prior to running slapd AND # should only be accessible by the slapd and slap tools. # Mode 700 recommended. directory /var/lib/ldap # Indices to maintain for this database index objectClass eq,pres index ou,cn,mail,surname,givenname eq,pres,sub index uidNumber,gidNumber,loginShell eq,pres index uid,memberUid eq,pres,sub index nisMapName,nisMapEntry eq,pres,sub # Our slapd-ldap back end to connect to AD database ldap suffix "dc=msad,dc=inet,dc=com" #subordinate rebind-as-user uri "ldap://172.16.132.253/" chase-referrals yes overlay rwm rwm-suffixmassage dc=msad,dc=inet,dc=com rwm-map attribute uid sAMAccountName rwm-map attribute cn cn rwm-map attribute displayName displayName rwm-map attribute givenName givenName rwm-map attribute sn sn rwm-map attribute mail mail rwm-map attribute userPassword userPassword rwm-map attribute * rwm-map objectclass inetOrgPerson user # Replicas of this database #replogfile /var/lib/ldap/openldap-master-replog #replica host=ldap-1.example.com:389 starttls=critical # bindmethod=sasl saslmech=GSSAPI # authcId=host/ldap-master.example.com(a)EXAMPLE.COM #* Any ideas as to why I'm unable to authenticate my user against the AD? Any advice or info on this topic would be greatly appreciated. Greetings, Jonathan Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and automatically archived by Mimecast SA (Pty) Ltd, an innovator in Software as a Service (SaaS) for business. Mimecast Unified Email Management (UEM) offers email continuity, security, archiving and compliance with all current legislation. To find out more, visit http://www.mimecast.co.za/uem-ppc.

2 3

how can make slave use tls to connect to master for syncrepl
by zhong ming wu 28 May '12

28 May '12

Hello I am using version 2.4 and in the process of setting up a master/slave pair using syncrepl. This is working as expected if I don't have enforce security and confidentiality with "security ssf=128" global directive in the master. As soon as I turn it on, replication stops working. It seems that the slave consumer is not using TLS to connect to master. However I can use 'ldapsearch' with '-ZZ' option to connect to master from slave and get all records I want. On my slave machine, I also have the following directive TLS_CACERT /etc/pki/tls/certs/ca.crt.crl in ldap.conf Notice that without this line 'ldapXXX' commands with '-ZZ' fails from slave to master. This confirms that at least 'ldap.conf' is in the correct location at least as far as 'ldapXXX' commands are concerned. Can someone point me in the right direction? I have read many chapters on this page http://www.openldap.org/doc/admin24/index.html Both slave and master are on centos 6.2 and openldap software is standard centos rpm. Here are the log entries on the master when slave fails to bind with TLS May 27 22:14:53 cat slapd[2456]: conn=1000 fd=13 ACCEPT from IP=192.168.0.2:41083 (IP=0.0.0.0:389) May 27 22:14:53 cat slapd[2456]: conn=1000 op=0 BIND dn="cn=root,dc=example,dc=com" method=128 May 27 22:14:53 cat slapd[2456]: conn=1000 op=0 RESULT tag=97 err=13 text=confidentiality required May 27 22:14:53 cat slapd[2456]: conn=1000 op=1 UNBIND May 27 22:14:53 cat slapd[2456]: conn=1000 fd=13 closed Sincerely Mr Wu

1 0

syncrepl for cn=config, changes fail with "tag=103 err=53 text=shadow context; no update referral"
by Elias Probst 28 May '12

28 May '12

Hi List, I'm trying to setup a master/master replication scenario, starting with getting cn=config replicated properly using OpenLDAP 2.4.30 on Gentoo. I've tried to start with a minimal config which is now up and running on both servers. As long as I start only one of both servers I can edit everything in cn=config just fine, but as soon as they both run at the same time, they get into a state which causes some trouble. Even shutting down one of both doesn't help then, I need to start from scratch again at this point. Submitting any changes results in this error message: RESULT tag=103 err=53 text=shadow context; no update referral There are two servers, connected via OpenVPN: ID 1, 10.44.0.1 ID 2, 10.44.0.7 I use the following configuration file to seed the initial online configuration for each server, before bringing them up both, using: slapd -f /tmp/slapd.conf -F /etc/openldap/slapd.d -u ldap -g ldap -d1 moduleload memberof.so moduleload syncprov.so moduleload refint.so include /etc/openldap/schema/core.schema include /etc/openldap/schema/cosine.schema include /etc/openldap/schema/inetorgperson.schema include /etc/openldap/schema/nis.schema include /etc/openldap/schema/openssh.schema TLSCACertificateFile /etc/ssl/slapd/slapd.cacrt TLSCertificateFile /etc/ssl/slapd/slapd.crt TLSCertificateKeyFile /etc/ssl/slapd/slapd.key TLSVerifyClient allow pidfile /var/run/openldap/slapd.pid argsfile /var/run/openldap/slapd.args loglevel 256 access to attrs=userPassword by self write by * auth access to * by * read ServerID 1 ldap://10.44.0.1 ServerID 2 ldap://10.44.0.7 backend bdb database config rootdn cn=config rootpw {SSHA}RI/d8i2R7XXlo2+kf2LcYzYOcIry+qaa syncrepl rid=001 provider="ldap://10.44.0.7" binddn="cn=config" bindmethod="simple" credentials="nothingtoseehere" searchbase="cn=config" type=refreshAndPersist retry="10 +" filter="(!(olcDatabase={0}config))" syncrepl rid=002 provider="ldap://10.44.0.1" binddn="cn=config" bindmethod="simple" credentials="nothingtoseehere" searchbase="cn=config" type=refreshAndPersist retry="10 +" filter="(!(olcDatabase={0}config))" overlay syncprov I don't quite understand the error message, as it somehow indicates the servers would be running in shadow context/MirrorMode, which is set to FALSE. So does anyone have an idea, what's wrong with my setup? Thanks a lot! - Elias

5 8

more on migrating from 2.3 to 2.4
by Bobby Krupczak 27 May '12

27 May '12

Hi! I did my nfs/nis/ldap/smb/dns swap this morning. I'm struggling with getting my ldap server to work as before. slapd is running and answering anonymous queries (like logging in and checking passwords) from other machines. >From the slapd host, I can do an ldapsearch (over ssl) and everything works. I authenticate as rootdn just fine. >From a different host, I cant do an ldapsearch; I receive an "invalid creditionals (49)" error. I have enabled debugging in ldapsearch and dont see anything interesting. The server ssl cert verifies fine. No config has changed on my client. I'm thinking its ssl, ipv6, and client cert related or maybe ACLs? In my slapd.conf file, I've put TLSVerifyClient never Any suggestions? slapd is 2.4.26-7.fc16.x86_64 Yes I know I'm running the fedora package. As soon as I can get the machine up and running as before I will start migrating. Thanks, Bobby

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openldap-technical May 2012