openldap-technical

openldap-technical@openldap.org

3 participants
9898 discussions

Segfault during Auth Benchmark request
by SAGNIMORTE Thomas (CAMPUS) 28 Apr '09

28 Apr '09

Hi, I am working on building and benchmarking OpenLDAP v2.4.16 for a large entries directory (actual test: 2 000 000 but final objective 10 000 000 users). I use SLAMD to test authentication in order to evaluate what is the maximum number of authentication I can do on my server. So I try to do 5 authentications per 5ms during 5min. My OpenLDAP 2.4.16 is install on the X86 two core 2.8Ghz server with 4Go of memory. I set 3Go in cache of DB_Config and I have look a lot on how configure properly slapd. Is it normal because I have reach system limits or can I change some parameter to optimize slapd performance? Do some people have some figures about slapd performance with large entries directory on standard server? Regards, --- Thomas

3 11

cannot rename back-sql tables
by Matthew Hallsworth 28 Apr '09

28 Apr '09

Hi list, I have searched far and wide for a solution to this but cannot find anywhere where it is possible to configure back-sql as such. I am trying to interface openldap with a MySQL backend using the standard back-sql configuration, with one exception - every 'ldap_*' prefixed table needs to be named 'custom_ldap_*' as we are trying to fit in LDAP support into an existing product which requires the additional tables to make this work to conform with existing schema. What I've found is, I can get the LDAP requests working perfectly via a test database using standard 'ldap_*' notation, but I cannot for the life of me get the system to handle different table names properly. My config file, "/etc/openldap/slapd.conf", on CentOS 5.2 shows the following: <snip> # # 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 # Allow LDAPv2 client connections. This is NOT the default. #allow bind_v2 loglevel -1 logfile /var/log/ldap.log # 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/lib64/openldap # modules available in openldap-servers-overlays RPM package: # moduleload accesslog.la # moduleload auditlog.la # moduleload denyop.la # moduleload dyngroup.la # moduleload dynlist.la # moduleload lastmod.la # moduleload pcache.la # moduleload ppolicy.la # moduleload refint.la # moduleload retcode.la # moduleload rwm.la # moduleload smbk5pwd.la # moduleload syncprov.la # moduleload translucent.la # moduleload unique.la # moduleload valsort.la # modules available in openldap-servers-sql RPM package: moduleload back_sql.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! ####################################################################### # sql definitions for mysql access ####################################################################### database sql dbname ldaptest readonly on suffix "dc=rams,dc=com,dc=au" dbuser ldaptest dbpasswd abc123 subtree_cond "custom_ldap_entries.dn LIKE CONCAT('%',?)" children_cond "custom_ldap_entries.dn LIKE CONCAT('%',?)" id_query "SELECT id,keyval,oc_map_id,dn FROM custom_ldap_entries WHERE dn=?" oc_query "SELECT id,name,keytbl,keycol,create_proc,delete_proc,expect_return FROM custom_ldap_oc_mappings" at_query "SELECT name,sel_expr,from_tbls,join_where,add_proc,delete_proc,param_order,expect_return,sel_expr_u FROM custom_ldap_attr_mappings WHERE oc_map_id=?" has_ldapinfo_dn_ru no lastmod off ####################################################################### # ldbm and/or bdb database definitions ####################################################################### #database bdb #suffix "dc=my-domain,dc=com" #rootdn "cn=Manager,dc=my-domain,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 {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 # 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 </snip> Now, when I run "/usr/sbin/slapd -d -5" and attempt to do a general query on the ldap server using "ldapsearch -x -b 'dc=rams,dc=com,dc=au'" I get the following feedback from openldap: <snip> # extended LDIF # # LDAPv3 # base <dc=rams,dc=com,dc=au> with scope subtree # filter: (objectclass=*) # requesting: ALL # # search result search: 2 result: 80 Other (e.g., implementation specific) error # numResponses: 1 </snip> And, the debug output displays: <snip> ... ==>backsql_search(): base="dc=rams,dc=com,dc=au", filter="(objectClass=*)", scope=2, deref=0, attrsonly=0, attributes to load: all ==>backsql_get_db_conn() ==>backsql_open_db_conn(3) daemon: epoll: listen=8 active_threads=0 tvp=NULL <==backsql_open_db_conn(3) backsql_open_db_conn(3): connected, adding to tree. <==backsql_get_db_conn() ==>backsql_dn2id("dc=rams,dc=com,dc=au") matched expected backsql_dn2id("dc=rams,dc=com,dc=au"): id_query "SELECT id,keyval,oc_map_id,dn FROM custom_ldap_entries WHERE dn=?" backsql_dn2id("dc=rams,dc=com,dc=au"): id=1 keyval=1 oc_id=1 dn=dc=rams,dc=com,dc=au >>> dnPrettyNormal: <dc=rams,dc=com,dc=au> <<< dnPrettyNormal: <dc=rams,dc=com,dc=au>, <dc=rams,dc=com,dc=au> <==backsql_dn2id("dc=rams,dc=com,dc=au"): err=0 ==>backsql_id2entry() backsql_id2entry(): retrieving all attributes ==>backsql_get_attr_vals(): oc="organizationalUnit" attr="objectClass" keyval=1 backsql_get_attr_vals(): error executing attribute count query 'SELECT COUNT(*) FROM ldap_entry_objclasses,ldap_entries,company WHERE company.id=? AND ldap_entries.id=ldap_entry_objclasses.entry_id AND ldap_entries.keyval=company.id and ldap_entries.oc_map_id=1' Return code: -1 nativeErrCode=1146 SQLengineState=S0002 msg="[unixODBC][MySQL][ODBC 3.51 Driver][mysqld-5.0.45]Table 'ldaptest.ldap_entry_objclasses' doesn't exist" <==backsql_id2entry() ==>backsql_oc_get_candidates(): oc="inetOrgPerson" ==>backsql_srch_query() ==>backsql_process_filter() <==backsql_process_filter() succeeded <==backsql_srch_query() returns SELECT DISTINCT ldap_entries.id,contact.id,'inetOrgPerson' AS objectClass,ldap_entries.dn AS dn FROM ldap_entries,contact WHERE contact.id=ldap_entries.keyval AND ldap_entries.oc_map_id=? AND 9=9 AND 3=3 Constructed query: SELECT DISTINCT ldap_entries.id,contact.id,'inetOrgPerson' AS objectClass,ldap_entries.dn AS dn FROM ldap_entries,contact WHERE contact.id=ldap_entries.keyval AND ldap_entries.oc_map_id=? AND 9=9 AND 3=3 id: '2' backsql_oc_get_candidates(): error executing query Return code: -1 nativeErrCode=1146 SQLengineState=S0002 msg="[unixODBC][MySQL][ODBC 3.51 Driver][mysqld-5.0.45]Table 'ldaptest.ldap_entries' doesn't exist" ==>backsql_oc_get_candidates(): oc="organizationalUnit" ==>backsql_srch_query() ==>backsql_process_filter() <==backsql_process_filter() succeeded <==backsql_srch_query() returns SELECT DISTINCT ldap_entries.id,company.id,'organizationalUnit' AS objectClass,ldap_entries.dn AS dn FROM ldap_entries,company WHERE company.id=ldap_entries.keyval AND ldap_entries.oc_map_id=? AND 9=9 AND 3=3 Constructed query: SELECT DISTINCT ldap_entries.id,company.id,'organizationalUnit' AS objectClass,ldap_entries.dn AS dn FROM ldap_entries,company WHERE company.id=ldap_entries.keyval AND ldap_entries.oc_map_id=? AND 9=9 AND 3=3 id: '1' backsql_oc_get_candidates(): error executing query Return code: -1 nativeErrCode=1146 SQLengineState=S0002 msg="[unixODBC][MySQL][ODBC 3.51 Driver][mysqld-5.0.45]Table 'ldaptest.ldap_entries' doesn't exist" send_ldap_result: conn=3 op=1 p=3 send_ldap_response: msgid=2 tag=101 err=80 ber_flush: 14 bytes to sd 9 0000: 30 0c 02 01 02 65 07 0a 01 50 04 00 04 00 0....e...P.... ldap_write: want=14, written=14 0000: 30 0c 02 01 02 65 07 0a 01 50 04 00 04 00 0....e...P.... conn=3 op=1 SEARCH RESULT tag=101 err=80 nentries=0 text= ... </snip> In summary, I feel that there is some kind of missing configuration variable either in documentation or tutorials online that really doesn't allow you to fully specify alternate table names for the default 4 main tables in the back-sql implementation. If this is due to the backend being experimental then so be it - however I really need some kind of quantified 'yes' or 'no' as to whether what I'm trying to achieve is possible at all. TIA Matthew Hallsworth

1 0

Re: bdb_equality_candidates warning
by Gustavo Mendes de Carvalho 28 Apr '09

28 Apr '09

Hi Quanah, I included this field to be indexed in ldap database, and after ldap restart I can't see this message anymore. Thanks for while. Gustavo 2009/4/27 Quanah Gibson-Mount <quanah(a)zimbra.com> > --On Monday, April 27, 2009 3:59 PM -0300 Gustavo Mendes de Carvalho < > gmcarvalho(a)gmail.com> wrote: > > Hi there, >> >> I have an OpenLDAP server version 2.3.39, and recentrly (I mean, since >> last friday) I noticed some delay when athenticating against LDAP base. >> >> I got this messages in ldap.log file >> >> Apr 27 15:46:39 ldap01 slapd[4445]: <= bdb_equality_candidates: >> (uniqueMember) not indexed >> > > Does anybody has some tip about it ? Which entry do I have to index to >> avoid this message ? Is there any way to find out which index is it >> caliming for ? >> > > Seems pretty clear to me. The log clearly states that the attribute > "uniqueMember" is not being indexed. Your index statements in slapd.conf > agree with that. > > --Quanah > > -- > > Quanah Gibson-Mount > Principal Software Engineer > Zimbra, Inc > -------------------- > Zimbra :: the leader in open source messaging and collaboration > -- Gustavo Mendes de Carvalho e-mail: gmcarvalho(a)gmail.com

3 3

RE:AW: Problem to Authenticate Users with openLDAP on Solaris 9
by panagiotis polychronopoulos 27 Apr '09

27 Apr '09

Actually, I do not have an ACL. Could you provide me further details for what I have to permit with the ACL. The log file of OpenLdapServer, when i execute the command "getent passwd on solaris" is the following: Apr 24 19:37:04 achilles slapd[22086]: conn=19 fd=10 ACCEPT from IP=10.0.0.25:33240 (IP=0.0.0.0:389) Apr 24 19:37:04 achilles slapd[22086]: conn=19 op=0 SRCH base="ou=people,dc=tesyd,dc=teimes,dc=gr" scope=2 deref=3 filter="(objectClass=posixAccount)" Apr 24 19:37:04 achilles slapd[22086]: conn=19 op=0 SRCH attr=cn uid uidnumber gidnumber gecos description homedirectory loginshell Apr 24 19:37:04 achilles slapd[22086]: conn=19 op=0 SEARCH RESULT tag=101 err=32 nentries=0 text= Apr 24 19:37:04 achilles slapd[22086]: conn=19 op=1 UNBIND Apr 24 19:37:04 achilles slapd[22086]: conn=19 fd=10 closed I have not declare the ou=people somewhere and i do not understand the searching on "ou=people,dc=tesyd,dc=teimes,dc=gr". any suggestion would help From: claus.kick(a)siemens.com To: poly_pan78(a)hotmail.com Date: Thu, 23 Apr 2009 16:06:21 +0200 Subject: AW: Problem to Authenticate Users with openLDAP on Solaris 9 Do you have an ACL in place in order to allow binding to read the ldap data? Von: openldap-technical-bounces+claus.kick=siemens.com(a)OpenLDAP.org [mailto:openldap-technical-bounces+claus.kick=siemens.com@OpenLDAP.org] Im Auftrag von panagiotis polychronopoulos Gesendet: Donnerstag, 23. April 2009 15:04 An: openldap-technical(a)openldap.org Betreff: Problem to Authenticate Users with openLDAP on Solaris 9 hi to everyone, I try to permit solaris 9 box to authenticate users with openLDAP Server. But I can not get access to "/etc/passwd" of LDAP Server. I have configured the solaris system as LDAP client with "ldapclient" command and I confirmed with the "ldapclient list" that give us the following: root@foivos:/> ldapclient list NS_LDAP_FILE_VERSION= 2.0 NS_LDAP_BINDDN= cn=Manager,dc=tesyd,dc=teimes,dc=gr NS_LDAP_BINDPASSWD= {NS1}5e10c25544515e26 NS_LDAP_SERVERS= 10.0.0.221 NS_LDAP_SEARCH_BASEDN= dc=tesyd,dc=teimes,dc=gr NS_LDAP_AUTH= simple NS_LDAP_SEARCH_SCOPE= sub NS_LDAP_SERVICE_AUTH_METHOD= pam_ldap:simple I also updated the /etc/nsswitch.conf but I still not get access to /etc/passwd file of LdapServer. It is checked by "getent passwd" Please, .any help would be appreciated Thanks in advance Δείξτε το στιλ σας με μια εικόνα στο Messenger. Δείτε τις όλες. Κάντε κλικ εδώ! Δείξτε το στιλ σας με μια εικόνα στο Messenger. Δείτε τις όλες. Κάντε κλικ εδώ! _________________________________________________________________ Έχετε Messenger; Έχετε και Windows Live. Μάθετε περισσότερα. http://www.microsoft.com/windows/windowslive

1 1

bdb_equality_candidates warning
by Gustavo Mendes de Carvalho 27 Apr '09

27 Apr '09

Hi there, I have an OpenLDAP server version 2.3.39, and recentrly (I mean, since last friday) I noticed some delay when athenticating against LDAP base. I got this messages in ldap.log file Apr 27 15:46:39 ldap01 slapd[4445]: <= bdb_equality_candidates: (uniqueMember) not indexed Apr 27 15:46:46 ldap01 slapd[4445]: <= bdb_equality_candidates: (uniqueMember) not indexed Apr 27 15:46:48 ldap01 slapd[4445]: <= bdb_equality_candidates: (uniqueMember) not indexed Apr 27 15:46:54 ldap01 slapd[4445]: <= bdb_equality_candidates: (uniqueMember) not indexed Apr 27 15:46:53 ldap01 slapd[4445]: <= bdb_equality_candidates: (uniqueMember) not indexed Apr 27 15:46:56 ldap01 slapd[4445]: <= bdb_equality_candidates: (uniqueMember) not indexed Apr 27 15:46:58 ldap01 slapd[4445]: <= bdb_equality_candidates: (uniqueMember) not indexed This is my slapd.conf related to indexes ####################################################################### # Indexes ####################################################################### index objectClass eq,pres index uid,memberUid eq,pres,sub I already checked for duplicate entries in ldif file, but I got nothing. Does anybody has some tip about it ? Which entry do I have to index to avoid this message ? Is there any way to find out which index is it caliming for ? Thanks in advance -- Gustavo Mendes de Carvalho e-mail: gmcarvalho(a)gmail.com

2 1

Re: slapd_db_archive log rotation
by Andrew Hall 27 Apr '09

27 Apr '09

Thanks for the reply Quanah. On 2009/4/25 Quanah Gibson-Mount wrote: > you fail to note what release you are using of OpenLDAP or BDB. There were > known issues with some earlier releases failing to checkpoint correctly. OpenLDAP 2.3.28 I've no idea the version of BDB - how would I find this out ? > You also fail to note your checkpoint parameter in slapd.conf. There doesn't seem to be a checkpoint setting in either slapd.conf or the DB_CONFIG file. Should there be ? > Also, rather than manually deleting logs, you can set BDB up to do it for you. See the > various options that can be set in DB_CONFIG. Yes, this can be specified with DB_LOG_AUTO_REMOVE but I wish to backup the log files before I remove them which is why I wish to do this manually.

2 3

Filter very strange problem for matching values
by Denis BUCHER 26 Apr '09

26 Apr '09

Hello everyone, I have a very strange problem with openldap... * Strange because it used to work and without reason (no update, no change in config) it suddently stopped to work * Strange because I have the correct configuration as far as I know * Strange because when I do tests, the results are illogical ! The problem is simple to explain, a filter doesn't work as expected ! The filter is : (&(objectclass=CourierMailAccount)(mail=%u)(accountStatus=active)) which mean find all object being : * in class CourierMailAccount * email is %u (this is replaced dynamically) * accountStatus is active The first two criteria are working, the problem is with accountStatus (if I remove this criteria it suddently works). PROBLEM : 1. if "accountStatus" is not present in my filter : it works 2. "accountStatus=active" => NO RESULTS ??? 3. "accountStatus=*" => RESULTS I tried in phpldaptadmin web interface, same problem : 1. "accountStatus=active" => NO RESULTS ??? 2. "accountStatus=*" => RESULTS In my schemas the config is : attributetype ( 1.3.6.1.4.1.7914.1.2.1.12 NAME 'accountStatus' DESC 'The status of a user account: active, noaccess, disabled, deleted' EQUALITY caseIgnoreIA5Match SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE ) Is therefore the problem with caseIgnoreIA5Match ? But this seems correct according to many web pages like http://www.zytrax.com/books/ldap/ape/qmail.html And it always worked before... Any help would be greatly appreciated because I don't see where the problem comes from ? (Maybe some index problem ???) Thanks a lot in advance Denis

2 1

slapd_db_archive log rotation
by Andrew Hall 25 Apr '09

25 Apr '09

Hi there. I'm using slapd_db_archive with the -a flag to identify BDB logs which can be safely deleted. I've recently noticed my logs are building up and -a does not produce any output. However the -l flag does successfully list the log files. Therefore any use of the -d flag to remove them does nothing. I'm almost certain these old logs are not being used (there's about 20 going back for several months now) but still slapd_db_archive does not pick up on them. Can anyone advise what may be happening here or how I can debug this further ? Thanks very much.

2 1

openldap as slave server to windows AD
by Aleksander Kamenik 24 Apr '09

24 Apr '09

Hi, This is my first experience with ldap, there are lots of different approaches to configuring openldap and I'm a bit lost. I'm about to setup a windows domain server with AD for some 50 windows pc's. The windows pc's will use the windows server directly and that's settled. However I also have lots of different services running on linux servers which require the same user authentication and could be configured to use ldap based authentication instead of each having their own account database. It's a hassle to maintain accounts for each service separately. Also, if the windows server should be unavailable, I'd still like to be able to login and use the services running on linux servers. So I imagine having openldap act a slave server (like in DNS) the for the windows active directory service's "User" space. Is this possible and which configuration path should I take? The manual mentions proxy configurations as well as something called chaining. Please point me to the correct chapter and any other hints are appreciated. Regards, -- Aleksander Kamenik System Administrator Krediidiinfo AS an Experian Company Phone: +372 665 9649 Email: aleksander(a)krediidiinfo.ee http://www.krediidiinfo.ee/ http://www.experiangroup.com/

2 1

Missing CSN in do_syncrep2 cookie log line
by Sean Burford 24 Apr '09

24 Apr '09

Hi, I'm new to 2.4 (2.4.16) and I don't know if empty CSNs are expected. The provider restarted and the syncrepl consumer kept sync, however part way through the reconnection the consumer got an empty CSN and decided to do an additional reconnect. This may be a side effect of the provider running 2.3.39. The provider has a syncrepl accesslog and an auditlog that both agree with the CSNs below (no changes were skipped by the sync). The accesslog database has syncprov-nopresent and syncprov-reloadhint set to TRUE. The main database has these values set to FALSE (syncprov-reloadhint will be toggled to TRUE shortly on the main database). At 13:20:42 username1 has an attribute removed. The change is replicated at that time. This is the last entry replicated before the provider is shut down: do_syncrep2: cookie=csn=20090424132042Z#000000#00#000000,rid=100 slap_queue_csn: queing 0xf966560 20090424132042Z#000000#00#000000 slap_graduate_commit_csn: removing 0x155621b8 20090424132042Z#000000#00#000000 syncrepl_message_to_op: rid=100 be_modify uid=username1,dc=example,dc=com (0) slap_queue_csn: queing 0xd2f6cf8 20090424132042Z#000000#00#000000 slap_graduate_commit_csn: removing 0xec0a758 20090424132042Z#000000#00#000000 At 13:25:18 slapd on the syncrepl provider is shut down and the consumer notices: do_syncrep2: rid=100 (-1) Can't contact LDAP server do_syncrepl: rid=100 rc -1 retrying At 13:26:12 slapd on the replication provider is restarted. The consumer connects 6 seconds later and receives the same attribute delete again (I assume it isn't an entry delete since there are no entry deletes in the hours bracketing this log): do_syncrep2: rid=100 LDAP_RES_INTERMEDIATE - REFRESH_DELETE do_syncrep2: cookie=csn=20090424132042Z#000000#00#000000,rid=100* do_syncrep2: cookie=csn=,rid=100* do_syncrepl: rid=100 rc -1 retrying At 13:27:18 slapd on the replication consumer reconnects and receives the same attribute delete again before continuing normal replication a little later when another user is modified: do_syncrep2: rid=100 LDAP_RES_INTERMEDIATE - REFRESH_DELETE do_syncrep2: cookie=csn=20090424132042Z#000000#00#000000,rid=100 do_syncrep2: cookie=csn=20090424133119Z#000000#00#000000,rid=100 slap_queue_csn: queing 0xc9fdb67 20090424133119Z#000000#00#000000 slap_graduate_commit_csn: removing 0xf610488 20090424133119Z#000000#00#000000 syncrepl_message_to_op: rid=100 be_modify uid=username2,dc=example,dc=com (0) -- Thanks, Sean Burford

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openldap-technical