openldap-software

openldap-software@openldap.org

2719 discussions

Re: openldap server migration issue
by Pierangelo Masarati 02 Sep '08

02 Sep '08

Please keep replies on the list. Naveen.X1.Sarabu(a)chase.com wrote: > Hi, > > On the current running prod server i have the same settings(acls). > users line is commented but "by * read " should allow users to read > the information. What I'm trying to tell you is that ACL parsing never gets to that "by * read" because it comes __after__ a commented out line. As such, that "by * read" is either a continuation of the comment or garbage. The fact that on the "current running prod server you have the same settings" is irrelevant. > i am suspecting it some thing to do with password scheme. in ldap all > passwprds are in {CRYPT}. I dont know in OS level what scheme it is > using and how to check? No, passwords are in whatever hash you created them (default {SSHA}), and {CRYPT} is the worst choice you could make. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ----------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Fax: +39 0382 476497 Email: ando(a)sys-net.it -----------------------------------

2 1

Re: Re: openldap server migration issue
by Gavin Henry 30 Aug '08

30 Aug '08

Yeah, good catch. I forgot to check acls. Sorry.

1 0

openldap server migration issue
by Naveen.X1.Sarabu＠chase.com 30 Aug '08

30 Aug '08

Hi, Can any one please help me in the following issue: Desc: I am in the process of migrating openldap from one server to antother server. current openldap server: server1.example.com new openldap server : server2.example.com Below is the procedure i have followed to migrate it: 1. setup server2.example.com as replica server of server1.example.com 2. after syncing the DB files , made it as standalone master ldap. for testing iam using the below commands: 1. when i search for info as Manager it is giving all the information server2#ldapsearch -x -b 'dc=example,dc=com' -D "cn=Manager,dc=example,dc=com" '(objectclass=*)' -H ldaps://server2.example.com -W 2. But when i try to search as a normal user it is throwing the following error. server2# ldapsearch -x -b 'dc=example,dc=com' -D "uid=okkamagadu,ou=People,dc=example,dc=com" '(objectclass=*)' -H ldaps://server2.example.com -W Enter LDAP Password: ldap_bind: Invalid credentials (49) <<<am i missing any configration,any suggestions? Here is My configureation information: # # See slapd.conf(5) for details on configuration options. # This file should NOT be world readable. # 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/openldap.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 /usr/sbin/openldap # moduleload back_bdb.la # moduleload back_ldap.la # moduleload back_ldbm.la # moduleload back_passwd.la # moduleload back_shell.la # The next three lines allow use of TLS for encrypting connections using a # dummy test certificate which you can generate by changing to # /usr/share/ssl/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 /usr/share/ssl/certs/ca-bundle.crt # TLSCertificateFile /usr/share/ssl/certs/slapd.pem # TLSCertificateKeyFile /usr/share/ssl/certs/slapd.pem TLSCACertificateFile /etc/openldap/ssl/certs/ca.crt TLSCertificateFile /etc/openldap/ssl/certs/server2.crt TLSCertificateKeyFile /etc/openldap/ssl/server2.key # 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 group.exact="cn=Admin,ou=LdapAdmin,dc=example,dc=com" write by * 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! ####################################################################### # ldbm and/or bdb database definitions ####################################################################### database bdb #suffix "dc=my-domain,dc=com" suffix "dc=example,dc=com" #rootdn "cn=Manager,dc=my-domain,dc=com" rootdn "cn=Manager,dc=example,dc=com" # 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 <password> # 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 # 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 ----------------------------------------- This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you.

3 5

olcServerID
by andylockran 30 Aug '08

30 Aug '08

http://blog.suretecsystems.com/archives/40-OpenLDAP-Weekly-News-Issue-5.html In the third box of code, this appears to set up the Master node with 3 serverIDs +URLS, when previously it was set up with a single serverID (which I assumed to be its identifier) is this correct? I'm running version 2.4.10 on both servers. Regards, Andy

3 4

OpenLDAP Date
by andylockran 30 Aug '08

30 Aug '08

Hi, I'm in the process of upgrading a 2.3.41 directory up to the 2.4 branch. I've got a few virtual machines with which I've been testing and running syncrepl. I've successfully 'pulled' all the data out from the old server (2.3) and that's now in database 1 on my new server. However, having installed openLDAP on another new server.. the date that logs are reporting is an hour earlier than the system time. Is there a configurable run-time option in slapd, to get the date? I've currently not got monitoring setup. Regards, Andy

4 4

slapadd bulk load performance issue
by Skulj Blaz 29 Aug '08

29 Aug '08

Hello, Version OpenLDAP: 2.4.11 OS: Linux Red Hat ES 4.6 Storage: Berkeley DB 4.2 (+4 patches) I'm testing performance in importing big LDIF file with 2 milions of entries (22.000.000 number of attributes). LDIF file is 600 MB big, one entry looks like this: dn: itContainerId=20000001,ou=Container,l=example,c=com objectClass: labeledURIObject objectClass: itContainerOC itContainerId: 20000001 itContainerType: 1 itContainerName: ljubljana1 itContainerStatus: 0 itParentContainerId: 3000000 itConfigurationNeeded: FALSE itSerialNumber: 04 itRegType: 1 I use slapadd tool with -q option : slapadd -q -f slapd.conf -l 2_milions_of_entry.ldif and the following configuration settings: database bdb dbcachesize 1000000 cachesize 150000 sizelimit 150000 checkpoint 10 1 set_cachesize 0 20000000 0 set_lg_regionmax 262144 set_lg_bsize 2097152 In my case, it takes about 20!!! hours to load the entire LDIF contents. Is this normal? Did anybody has experiences with loading of such amount of data? Am i perhaps having wrong settings in config file? Can you please someone tell me, how much time is normaly needed for slapadd? Thanks for your help. Best Regards Blaz Skulj

2 1

unique id required
by Arpit Jain 29 Aug '08

29 Aug '08

Dear List Members, OpenLDAP version 2.3.39 on RHEL5 I am using "OpenLDAP " to store information. This information is retrieved by a "client" and made available to "user" via the vfs(virtual fire system) interface in linux. The user then reads/writes/browses the information just like in a filesystem. I can store a 64-bit id of each entry as inode number in my client. A "unique id" of size 64-bits is required for each entry so that once an entry is searched by giving "dn", further searches for the entry can be done using that unique id. The unique id must be in some way auto-generated by openldap server. entryUUID has been identified to fulfills all the requirements except that it is 128-bit long. I would like to know if there is some other operational attribute which is unique for each entry and of size 64-bits? of if I can extract a 64-bit unique value from entryUUID or any other attribute? If required the operation can be shifted to some other version of OpenLDAP also. Arpit J. Center for Development of Advanced Computing (C-DAC) http://www.cdac.in

1 0

BDB and cache settings - anything wrong? userPassword field keeps getting corrupted.
by k bah 29 Aug '08

29 Aug '08

I have one LDAP master server, a test server, which no one but me has access to (at least I think). Something really strange is happening, userPassword fields (they are in MD5 format) keep getting changed every 1 or 2 days. Sometimes they change after a mass add operation, or mass delete operation. It could be someone messing with me, but that would be unusual, since they also happen after I do mass operations on the server. I rechecked my "mass operation" scripts, and they do not seem to be breaking other entries while they operate on a given entry (add/delete entry and bind with that DN). I think maybe my BDB and cache settings may be causing it, it's just a thought, I really don't know what's going on: I have about 15000 entries on my server, they will grown around 1000 each 6 months. My slapd.conf --- include /etc/openldap/schema/core.schema include /etc/openldap/schema/cosine.schema include /etc/openldap/schema/inetorgperson.schema include /etc/openldap/schema/rfc2307bis.schema include /etc/openldap/schema/yast.schema include /etc/openldap/schema/postfix.schema include /etc/openldap/schema/misc.schema include /etc/openldap/acl-ldap.conf schemacheck on allow bind_v2 pidfile /var/run/slapd/slapd.pid argsfile /var/run/slapd/slapd.args modulepath /usr/lib/openldap/modules database bdb suffix "dc=organization,dc=com,dc=tld" cachesize 16500 rootdn "cn=donotusethisdn,dc=organization,dc=com,dc=tld" rootpw {MD5}blablabla checkpoint 1024 5 loglevel any lastmod on SIZELIMIT -1 directory /var/lib/ldap index objectClass eq,pres # 2008-07-25 index ou,cn,mail,sn,givenname eq,pres,sub # 2008-06-31 index uid,memberUid,mailacceptinggeneralid,maildrop pres,eq index mailroutingaddress pres,eq TLSCertificateFile /etc/openldap/cert.crt TLSCertificateKeyFile /etc/openldap/key.key TLSCACertificateFile /etc/openldap/cacert.crt replica uri=ldap://ldapslave.organization.com.tld:389 binddn=cn=slavereplicator,ou=adm,dc=organization,dc=com,dc=tld bindmethod=simple credentials=blebleble starttls=critical replogfile /var/lib/ldap/replog --- slapd.conf --- /var/lib/ldap/DB_CONFIG set_cachesize 0 64781516 1 set_lg_regionmax 262144 set_lg_bsize 2097152 set_flags DB_LOG_AUTOREMOVE --- /var/lib/ldap/DB_CONFIG --------------- server: # ls -lh /var/lib/ldap/*.bdb -rw------- 1 ldap ldap 6.2M Aug 28 08:58 /var/lib/ldap/cn.bdb -rw------- 1 ldap ldap 3.3M Aug 28 08:58 /var/lib/ldap/dn2id.bdb -rw------- 1 ldap ldap 4.8M Aug 28 08:58 /var/lib/ldap/givenName.bdb -rw------- 1 ldap ldap 20M Aug 28 08:58 /var/lib/ldap/id2entry.bdb -rw------- 1 ldap ldap 11M Aug 28 08:58 /var/lib/ldap/mail.bdb -rw------- 1 ldap ldap 816K Aug 28 08:58 /var/lib/ldap/mailRoutingAddress.bdb -rw------- 1 ldap ldap 8.0K Aug 22 15:55 /var/lib/ldap/memberUid.bdb -rw------- 1 ldap ldap 2.0M Aug 28 08:58 /var/lib/ldap/objectClass.bdb -rw------- 1 ldap ldap 8.0K Aug 22 15:55 /var/lib/ldap/ou.bdb -rw------- 1 ldap ldap 8.7M Aug 28 08:58 /var/lib/ldap/sn.bdb -rw------- 1 ldap ldap 804K Aug 28 08:58 /var/lib/ldap/uid.bdb --------------- These cache settings make sense? The "corruptions", if I can call them that, are also happening on the slave, master and slave are exactly equal (slapcat's output is exact the same), so I rule out that the replication is causing this. Before "checkpoint 1024 5" on slapd.conf was "checkpoint 512 15". I'm turning replication off, and I'll see what happens. I really don't understand what's going on, an attacker messing with me would be really strange, since he does not have access to anything with these passes, and he could do a lot of other more obvious things to mess with my work, I don't know, deleting something....but at the same time, it's strange to get data corrupted and _just_ this particular field. Other fields on the entries are not altered. = -- Powered by Outblaze

4 3

hdb search performance
by tamarin p 28 Aug '08

28 Aug '08

I've been running some tests with OpenLDAP 2.4.11 lately, with an existing application that will use the LDAP as its backend for storing users and roles. Using bdb, performance is excellent. With hdb on the other hand, the application is rendered unusable unless the searched entry is already cached, as one particular search takes minutes to execute otherwise, whereas in bdb the same search quite fast regardless. The specific search is subtree (scope=2 deref=0) filtered on "o" and "objectclass" like so: (&(objectClass=organization)(o=123456)).. Both attributes have equality indexes. The whole directory has just over 4 million entries, and about 500.000 of those are in the context being searched thanks to the scope. The strange thing is how bdb is fast from search one, while hdb with hdb it takes minutes to complete unless the entry is already cached. I've tried configuring caches according to the faq-o-matic. The docs mention that hdb requires a bigger idl cache in particular, to have good search performance, so I've tried various cache sizes, up to 1 million for idl- and 330.000 for the entry caches, but this seems to make slapd dig so deeply into virtual memory that I'm not sure if it actually does more harm than good. As for DB_CONFIG, I've reused the same DB_CONFIG for both backends and configured according to the faq-o-matic as far as I can tell, then doubled (and then some) the size I came up with to be on the safe side with regards to overhead and such. dn2id with pagesize 4096 and approx 9300 internal pages, and id2entry with pagesize 16k and 300 internal pages and I've allocated 256mb to the dbcache which should be a lot more than the ~50mb minimum required I ended up with for internal pages and any overhead. Also tried bumping this to 512MB but as the faq-o-matic entry suggests, this doesn't seem to have any effect really. Now, there's no requirement to use hdb as the application doesn't need subtree renames and bdb works great. I just want check that my config isn't horribly wrong, or that I'm overlooking something vital for hdb not required for bdb..

3 3

Lock table is out of available object entries
by Reynaldo Quezada V. 28 Aug '08

28 Aug '08

I tried the next solutions... 1.- I charge the DB with slapadd, since one backup but when I Charge other group with 1500 users the error occurs again... ldap_modify: Internal (implementation specific) error (80) 2.- I delete the group from the backup and charge the DB withouth problems, but when I charge the group by separated, the error occurs again. ldap_modify: Internal (implementation specific) error (80) 3.- I started the slapd in debug level 3 and charge the group by separately and this is the exit.... bdb(dc=gtk.org): Lock table is out of available object entries => bdb_idl_insert_key: c_get failed: Cannot allocate memory (12) <= key_change 12 <= index_entry_add( 21187, "cn=obs.capture,ou=grupos,dc=gtk.org" ) failure bdb_add: index_entry_add failed send_ldap_result: conn=3 op=1 p=3 send_ldap_response: msgid=2 tag=105 err=80 ber_flush: 37 bytes to sd 13 0000: 30 23 02 01 02 69 1e 0a 01 50 04 00 04 17 69 6e 0#...i...P....in 0010: 64 65 78 20 67 65 6e 65 72 61 74 69 6f 6e 20 66 dex generation f 0020: 61 69 6c 65 64 ailed ldap_write: want=37, written=37 0000: 30 23 02 01 02 69 1e 0a 01 50 04 00 04 17 69 6e 0#...i...P....in 0010: 64 65 78 20 67 65 6e 65 72 61 74 69 6f 6e 20 66 dex generation f 0020: 61 69 6c 65 64 ailed connection_get(13): got connid=3 connection_read(13): checking for input on id=3 ber_get_next ldap_read: want=8, got=7 0000: 30 05 02 01 03 42 00 0....B. ber_get_next: tag 0x30 len 5 contents: ber_get_next ldap_read: want=8, got=0 ber_get_next on fd 13 failed errno=0 (Success) connection_read(13): input error=-2 id=3, closing. connection_closing: readying conn=3 sd=13 for close connection_close: deferring conn=3 sd=13 do_unbind connection_resched: attempting closing conn=3 sd=13 connection_close: deferring conn=3 sd=13 connection_resched: attempting closing conn=3 sd=13 connection_close: conn=3 sd=13 connection_get(13): connection not used connection_read(13): no connection! daemon: shutdown requested and initiated. slapd shutdown: waiting for 0 threads to terminate slapd shutdown: initiated ====> bdb_cache_release_all slapd destroy: freeing system resources. 4.- I was learning about this error and make some tunning to the memory's parameters but the error persist the configuration in the DB_CONFIF is... set_cachesize 0 1610612736 1 set_lk_max_locks 1048576 # Set database flags. # (for database loading/reindexing) #set_flags DB_TXN_NOSYNC # Set log values. # set_lg_regionmax 31457280 set_lg_max 20971520 set_lg_bsize 4194304 set_lg_dir /var/lib/ldap Thanks a lot! Reynaldo Quezada L.I. UNAM __________________________________________________ Correo Yahoo! Espacio para todos tus mensajes, antivirus y antispam ¡gratis! Regístrate ya - http://correo.yahoo.com.mx/

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-software