openldap-software August 2007

openldap-software@openldap.org

77 participants
93 discussions

multiple attribute list need
by Paul Ghosh 13 Aug '07

13 Aug '07

There is an application that needs to display multiple lists of people with their email address. The number of lists and the content of the lists we would like to leave configurable in LDAP. So, we set up a few dynamic lists in LDAP, put them into a 'groupOfUniqueNames' object which the application retrieved, and then in turn queried the dynamic lists to obtain the contents of the lists. We ran into three challenges: First, since dynamic lists follow the schema definition rules it could not return multiple values for the attribute 'displayName' so we configured it for 'givenName' instead. Second, it returned the results grouped by email address and names instead of pairs of data so we walked through all the email addresses and then the names while confirming the counts were the same and assuming that they were in the same order. Third, if an email address or name was missing then the manual pairing of data would be incorrect so we put in a filter that ensures only members with both pieces of data were included. Ideally we would like to retrieve pairs of full names and email addresses. The following does provide the information to us in the preferred format: ldapsearch -a never -h xxx.xxx.xxx.xxx -b "ou=people,dc=example,dc=com" -x (&(&(departmentNumber=other)(mail=*))(displayName=*))" displayName mail # extended LDIF # # LDAPv3 # base <ou=people,dc=example,dc=com> with scope subtree # filter: (&(&(departmentNumber=other)(mail=*))(displayName=*)) # requesting: displayName mail # # root, people, example.com dn: uid=root,ou=people,dc=example,dc=com mail: root(a)example.com displayName: root # nobody, people, example.com dn: uid=nobody,ou=people,dc=example,dc=com displayName: nobody mail: nobody(a)example.com # jsmith, people, example.com dn: uid=jsmith,ou=people,dc=example,dc=com mail: jsmith(a)example.com displayName: John Smith # search result search: 2 result: 0 Success # numResponses: 4 # numEntries: 3 An equivalent is the following which is set up as a 'memberURL' attribute of a 'groupOfURLs' object with the exception of 'givenName' instead of 'displayName' because of dynamic list adherence to schema definitions: ldap:///ou=people,dc=example,dc=com?mail,givenName?sub?(&(&(departmentNumber =other)(mail=*))(givenName=*)) ldapsearch -a never -h xxx.xxx.xxx.xxx -b "cn=other,ou=lists,dc=example,dc=com" -x # extended LDIF # # LDAPv3 # base <cn=other,ou=lists,dc=example,dc=com> with scope subtree # filter: (objectclass=*) # requesting: ALL # # other, lists, example.com dn: cn=other,ou=lists,dc=example,dc=com cn: other objectClass: groupOfURLs objectClass: top memberURL: ldap:///ou=people,dc=example,dc=com?mail,givenName?sub?(&(&(departmentNumber =other)(mail=*))(givenName=*)) mail: root(a)example.com mail: nobody(a)example.com mail: jsmith(a)example.com givenName: root givenName: nobody givenName: John Smith member: uid=root,ou=people,dc=example,dc=com member: uid=nobody,ou=people,dc=example,dc=com member: uid=jsmith,ou=people,dc=example,dc=com # search result search: 2 result: 0 Success # numResponses: 2 # numEntries: 1 Is there a way to accomplish what the regular search returns using openldap features?

2 4

access accesslog: how do I search for modifications under a subtree?
by Zhang Weiwu 13 Aug '07

13 Aug '07

Dear everyone I use accesslog and is pretty fond of it. Recently I need to look up several deleted entries, who deleted them and when, who modified these entries before deletion. And I found it not easy. All the clue I have is the deleted entries, before they are deleted, are in certain subtree. I first thought I can do a search like this: ldapsearch ...(accesslog db)... '(reqDn=*uid=dep1,ou=contacts,dc=example,dc=com)' Where 'uid=dep1,ou=contacts,dc=example,dc=com' is the parent node of the node that was deleted. This doesn't work (always return no result). I guess one reason is wildcard search is not allowed in reqDn for certain reason. The second idea is to dump while accesslog database and do some grepping and awking around it. But that way the whole means of using ldap database for accesslog is lost. The reason of using ldapdatabase for accesslog, rather than a plain text file, is to be able to search for modification records without having to do grepping and awking (especially grepping might be diffcult because the dn might been base64 encoded in ldif dumped from database) So again can someone with experience show what you would do in this case? Thanks a lot!

2 1

How can i use TLS_CACERT in client and in server side
by sridhar varadarajan 13 Aug '07

13 Aug '07

I am giving list of CA`s in server side in SLAPD.CONF and i refered that same certificates in client side but its throwing error in client side that : TLS couldnt use the locations. Can any one tell me the syntax to mention in server and in client side. thanks in advance With regards, sri

2 1

TLS failure when running OpenLDAP 2.3.30 on Debian 4.0
by Erling Ringen Elvsrud 10 Aug '07

10 Aug '07

Hello, I just upgraded to Debian 4.0 and OpenLDAP 2.3.30 and have some problems starting slapd afterwards. With TLS enabled I get this output in syslog when running /etc/init.d/slapd start: Aug 10 10:27:43 localhost slapd[10057]: daemon: IPv6 socket() failed errno=97 (Address family not supported by protocol) Aug 10 10:27:43 localhost slapd[10057]: /etc/ldap/slapd.access: line 11: rootdn is always granted unlimited privileges. Aug 10 10:27:46 localhost slapd[10057]: main: TLS init def ctx failed: -1 Aug 10 10:27:46 localhost slapd[10057]: slapd stopped. Aug 10 10:27:46 localhost slapd[10057]: connections_destroy: nothing to destroy. If I disable TLS slapd starts without any errors. Any clue what the "main: TLS init def ctx failed:" means is appreciated. Thanks, Erling

3 2

Problems changing passwords
by Rick Tautin 10 Aug '07

10 Aug '07

I am unable to change users passwords as themselves. When a user tries to change their password, they get and error invalid credentials(49). I have tried every option of changing the acl's to allow them to bind and change it but nothing has worked. Any help would be appreciated. Here is my slapd.conf and the command I am trying to use to change the password. ldappasswd -x -D "uid=user1,ou=users,ou=employees,ou=users,dc=example,dc=com" -w tt#12345 -s new#1234 uid=user1,ou=users,ou=employees,ou=users,dc=example,dc=com # See slapd.conf(5) for details on configuration options. # This file should NOT be world readable. # include /usr/local/etc/openldap/schema/core.schema include /usr/local/etc/openldap/schema/cosine.schema include /usr/local/etc/openldap/schema/nis.schema include /usr/local/etc/openldap/schema/inetorgperson.schema include /usr/local/etc/openldap/schema/misc.schema # Define global ACLs to disable default read access. # Do not enable referrals until AFTER you have a working directory # service AND an understanding of referrals. #referral ldap://root.openldap.org pidfile /usr/local/var/run/slapd.pid argsfile /usr/local/var/run/slapd.args # Load dynamic backend modules: # modulepath /usr/local/libexec/openldap # moduleload back_bdb.la # moduleload back_ldap.la # moduleload back_ldbm.la # moduleload back_passwd.la # moduleload back_shell.la #tru64 bind allow bind_v2 # 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 TLSCACertificateFile /usr/local/etc/openldap/cacert.pem TLSCertificateFile /usr/local/etc/openldap/servercrt.pem TLSCertificateKeyFile /usr/local/etc/openldap/serverkey.pem # 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 * read # 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! ####################################################################### # BDB database definitions ####################################################################### database bdb suffix "dc=example,dc=com" rootdn "cn=Manager,dc=example,dc=com" # Cleartext passwords, especially for the rootdn, should # be avoid. See slappasswd(8) and slapd.conf(5) for details. # Use of strong authentication encouraged. rootpw {SSHA}OIbjYF+qgnf6+yiF+QvFMKhUONMmRp1q # The database directory MUST exist prior to running slapd AND # should only be accessible by the slapd and slap tools. # Mode 700 recommended. directory /usr/local/var/openldap-data # Indices to maintain index objectClass eq index cn,uid eq index uidNumber eq index gidNumber eq index userPassword eq #logging loglevel 512 #cache size cachesize 2000

3 5

regarding data backup
by Arunachalam Parthasarathy 10 Aug '07

10 Aug '07

Hello all, I am using openldap 2.3.36. Is it better to use slapcat to backup the data and use it during recovery (after disk partition crash) using slapadd ? Or backup the transaction log files of BDB , so that recovery will be done using openldap's automatic recovery functionality or dbrecover utility of bdb ? Please correct me if I am wrong in the process of data maintenance. Thanks in advance, Arunachalam. **************************************************************************** **************************** This e-mail and attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient's) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!

5 4

Deleting a referral?
by Hadmut Danisch 10 Aug '07

10 Aug '07

Hi, I have created a referral for test purposes: dn: cn=test,... cn: test objectClass: top objectClass: referral objectClass: extensibleObject ref: xyz but ldapdelete does not remove it anymore. When I try to delete it I get the error message ldap_delete: Referral (10) matched DN: cn=test,... referrals: xyz How would I tell ldapdelete to immediately delete it without trying to follow the referral? regards Hadmut

4 4

strange search result, cn=* seems not working properly
by Zhang Weiwu 10 Aug '07

10 Aug '07

Dear everyone on the list I have seen this very strange behavior on our ldap first time in 3 years of running openldap, my strange case can be explained with these two searches, the first search (cn=Dirk Bonge*) returns an entry with RDN as "cn=Dirk Bonges" and the second search (cn=*) returns many entry but missed "cn=Dirk Bonges" (which should be included), rest of the two search command are exactly the same: $ ldapsearch -D xxx -b uid=PricewaterhouseCoopers_0,ou=contacts,ou=china,dc=com,dc=de "cn=Dirk Bonge*" dn cn # extended LDIF # # LDAPv3 # base <uid=PricewaterhouseCoopers_0,ou=contacts,ou=china,dc=com,dc=de> with scope subtree # filter: cn=Dirk Bonge* # requesting: dn cn # # Dirk Bongers, PricewaterhouseCoopers_0, contacts, china, ahk.de dn: cn=Dirk Bongers,uid=PricewaterhouseCoopers_0,ou=contacts,ou=china,dc=com,d c=de cn;lang-py: shen zhi bo cn: Dirk Bongers # Dirk Bonger, PricewaterhouseCoopers_0, contacts, china, ahk.de dn: cn=Dirk Bonger,uid=PricewaterhouseCoopers_0,ou=contacts,ou=china,dc=com,dc =de cn: Dirk Bonger cn;lang-de:: IA== # search result search: 2 result: 0 Success # numResponses: 3 # numEntries: 2 $ ldapsearch -D xxx -b uid=PricewaterhouseCoopers_0,ou=contacts,ou=china,dc=com,dc=de "cn=*" dn cn # extended LDIF # # LDAPv3 # base <uid=PricewaterhouseCoopers_0,ou=contacts,ou=china,dc=com,dc=de> with scope subtree # filter: cn=* # requesting: dn cn # # Edward Shum, PricewaterhouseCoopers_0, contacts, china, ahk.de dn: cn=Edward Shum,uid=PricewaterhouseCoopers_0,ou=contacts,ou=china,dc=com,dc =de cn: Edward Shum cn;lang-zh:: 5rKI56ia5rOi cn;lang-py: shen zhi bo # Dirk Bonger, PricewaterhouseCoopers_0, contacts, china, ahk.de dn: cn=Dirk Bonger,uid=PricewaterhouseCoopers_0,ou=contacts,ou=china,dc=com,dc =de cn: Dirk Bonger cn;lang-de:: IA== # Tao Xu, PricewaterhouseCoopers_0, contacts, china, ahk.de dn: cn=Tao Xu,uid=PricewaterhouseCoopers_0,ou=contacts,ou=china,dc=com,dc=de cn: Tao Xu # Anke Schrader, PricewaterhouseCoopers_0, contacts, china, ahk.de dn: cn=Anke Schrader,uid=PricewaterhouseCoopers_0,ou=contacts,ou=china,dc=com, dc=de cn: Anke Schrader # search result search: 2 result: 0 Success # numResponses: 5 # numEntries: 4 I don't know what further information I should provide (e.g. which section of the slapd.conf should I provide), the OS is Debian Etch and we use openldap 2.3.27. we used accesslog overlay and refint overlay, backend is hdb. Please let me know what I should provide. Thanks very much in advance! Best Regards -- Zhang Weiwu

1 0

Problem with back-sql after update from 2.2 to 2.3
by Andreas 'ads' Scherbaum 09 Aug '07

09 Aug '07

Hello all, i tried to update an openldap server from 2.2.13 to 2.3.27 but ran into problems. The slapd is using back-sql to get data from an existing PostgreSQL groupware database. This worked fine with the 2.2 version, but after the update the client (Thunderbird in my case) no longer gets data. According to wireshark, no data is sent back to the client. Testing with a local ldapsearch brings results, but with the following differences: ----- 2.2.13 ----- objectClass: orgPerson objectClass: inetOrgPerson objectClass: officePerson objectClass: evolutionPerson objectClass: top objectClass: opengroupwareentity objectClass: person ----- 2.2.13 ----- ----- 2.3.27 ----- objectClass: person objectClass: evolutionPerson objectClass: inetOrgPerson objectClass: opengroupwareentity objectClass: top ----- 2.3.27 ----- The 'ldap_objectclass_list' table contains the following entries: ----- cut ----- OGo=# select * from ldap_objectclass_list; oc_map_id | objectclass -----------+--------------------- 1 | orgPerson 1 | inetOrgPerson 1 | officePerson 1 | evolutionPerson 1 | top 1 | opengroupwareentity 3 | top 3 | opengroupwareentity 4 | top 4 | domainRelatedObject (10 rows) ----- cut ----- Has anybody an idea why the ldapsearch returns fewer entries for the objectClass? That should be the reason, why no data is sent back to the client. Kind regards -- Andreas 'ads' Scherbaum Failure is not an option. It comes bundled with your Microsoft product. (Ferenc Mantfeld)

2 3

olcPasswordHash scheme not available
by Mustafa A. Hashmi 09 Aug '07

09 Aug '07

OS: Debian Etch Openldap version: 2.3.30 Hi all: Moving towards housing configuration data within openldap, I have the directory working correctly and reading cn=config without any issues. However, if the password-hash {K5KEY} is specified, slapd refuses to start and immediately reports: olcPasswordHash: value #0: <olcPasswordHash> scheme not available ({K5KEY}) olcPasswordHash: value #0: <olcPasswordHash> no valid hashes found config error processing cn=config: <olcPasswordHash> no valid hashes found I am guessing this has to do with the order modules and configuration are loaded -- however, I am not at all sure. The smbk5pwd module is loaded and the hash directive works correctly via slapd.conf. Any help would be much appreciated. thank you, -- Mustafa A. Hashmi mahashmi(a)gmail.com

3 6

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-software August 2007