openldap-technical

openldap-technical@openldap.org

21 participants
9802 discussions

ldapbin : Invalid DN Syntax (34)
by Joseph vasanth 07 Oct '11

07 Oct '11

Hi, I am a newbie on openldap. I have just installed openldap on FC11. I am facing issues when i try to bind. When i do an ldapsearch it throws the ldapbin : Invalid DN Syntax (34) error. I have the following information slapd.conf # # 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. #referralldap://root.openldap.org pidfile/var/run/openldap/slapd.pid argsfile/var/run/openldap/slapd.args # Load dynamic backend modules: # modulepath/usr/lib/openldap # or /usr/lib64/openldap # moduleload accesslog.la # moduleload auditlog.la # moduleload back_sql.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 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! ####################################################################### # ldbm and/or bdb database definitions ####################################################################### databasebdb suffix"dc=primecorp,dc=com" checkpoint1024 15 rootdn"cn=Manager,dc=primecorp,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. rootpwpassword rootpw{MD5}X03MO1qnZdYdgyfeuILPmQ== # 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 # enable monitoring database monitor access to attrs=userPassword by self write by dn="cn=Manager,dc=primecorp,dc=com" write by anonymous auth by * none # allow onlu rootdn to read the monitor access to * by dn="cn=Manager,dc=primecorp,dc=com" write by self write by * read /etc/ldap.conf # # LDAP Defaults # # See ldap.conf(5) for details # This file should be world readable but not world writable. #BASEdc=example,dc=com #URIldap://ldap.example.com ldap://ldap-master.example.com:666 #SIZELIMIT12 #TIMELIMIT15 #DEREFnever URI ldap://127.0.0.1/ BASE dc=primecorp,dc=com TLS_CACERTDIR /etc/openldap/cacerts /etc/opnldap/ldap.conf # @(#)$Id: ldap.conf,v 1.38 2006/05/15 08:13:31 lukeh Exp $ # # This is the configuration file for the LDAP nameservice # switch library and the LDAP PAM module. # # The man pages for this file are nss_ldap(5) and pam_ldap(5) # # PADL Software # http://www.padl.com # # Your LDAP server. Must be resolvable without using LDAP. # Multiple hosts may be specified, each separated by a # space. How long nss_ldap takes to failover depends on # whether your LDAP client library supports configurable # network or connect timeouts (see bind_timelimit). #host 127.0.0.1 # The distinguished name of the search base. base dc=primecorp,dc=com # Another way to specify your LDAP server is to provide an # uri with the server name. This allows to use # Unix Domain Sockets to connect to a local LDAP Server. #uri ldap://127.0.0.1/ #uri ldaps://127.0.0.1/ #uri ldapi://%2fvar%2frun%2fldapi_sock/ # Note: %2f encodes the '/' used as directory separator # The LDAP version to use (defaults to 3 # if supported by client library) #ldap_version 3 # The distinguished name to bind to the server with. # Optional: default is to bind anonymously. #binddn cn=proxyuser,dc=example,dc=com # The credentials to bind with. # Optional: default is no credential. #bindpw secret # The distinguished name to bind to the server with # if the effective user ID is root. Password is # stored in /etc/ldap.secret (mode 600) #rootbinddn cn=manager,dc=example,dc=com # The port. # Optional: default is 389. #port 389 # The search scope. #scope sub #scope one #scope base # Search timelimit #timelimit 30 timelimit 120 # Bind/connect timelimit #bind_timelimit 30 bind_timelimit 120 # Reconnect policy: hard (default) will retry connecting to # the software with exponential backoff, soft will fail # immediately. #bind_policy hard # Idle timelimit; client will close connections # (nss_ldap only) if the server has not been contacted # for the number of seconds specified below. #idle_timelimit 3600 idle_timelimit 3600 # Filter to AND with uid=%s #pam_filter objectclass=account # The user ID attribute (defaults to uid) #pam_login_attribute uid # Search the root DSE for the password policy (works # with Netscape Directory Server) #pam_lookup_policy yes # Check the 'host' attribute for access control # Default is no; if set to yes, and user has no # value for the host attribute, and pam_ldap is # configured for account management (authorization) # then the user will not be allowed to login. #pam_check_host_attr yes # Check the 'authorizedService' attribute for access # control # Default is no; if set to yes, and the user has no # value for the authorizedService attribute, and # pam_ldap is configured for account management # (authorization) then the user will not be allowed # to login. #pam_check_service_attr yes # Group to enforce membership of #pam_groupdn cn=PAM,ou=Groups,dc=example,dc=com # Group member attribute #pam_member_attribute uniquemember # Specify a minium or maximum UID number allowed #pam_min_uid 0 #pam_max_uid 0 # Template login attribute, default template user # (can be overriden by value of former attribute # in user's entry) #pam_login_attribute userPrincipalName #pam_template_login_attribute uid #pam_template_login nobody # HEADS UP: the pam_crypt, pam_nds_passwd, # and pam_ad_passwd options are no # longer supported. # # Do not hash the password at all; presume # the directory server will do it, if # necessary. This is the default. #pam_password clear # Hash password locally; required for University of # Michigan LDAP server, and works with Netscape # Directory Server if you're using the UNIX-Crypt # hash mechanism and not using the NT Synchronization # service. #pam_password crypt # Remove old password first, then update in # cleartext. Necessary for use with Novell # Directory Services (NDS) #pam_password clear_remove_old #pam_password nds # RACF is an alias for the above. For use with # IBM RACF #pam_password racf # Update Active Directory password, by # creating Unicode password and updating # unicodePwd attribute. #pam_password ad # Use the OpenLDAP password change # extended operation to update the password. #pam_password exop # Redirect users to a URL or somesuch on password # changes. #pam_password_prohibit_message Please visit http://internal to change your password. # RFC2307bis naming contexts # Syntax: # nss_base_XXXbase?scope?filter # where scope is {base,one,sub} # and filter is a filter to be &'d with the # default filter. # You can omit the suffix eg: # nss_base_passwdou=People, # to append the default base DN but this # may incur a small performance impact. #nss_base_passwdou=People,dc=example,dc=com?one #nss_base_shadowou=People,dc=example,dc=com?one #nss_base_groupou=Group,dc=example,dc=com?one #nss_base_hostsou=Hosts,dc=example,dc=com?one #nss_base_servicesou=Services,dc=example,dc=com?one #nss_base_networksou=Networks,dc=example,dc=com?one #nss_base_protocolsou=Protocols,dc=example,dc=com?one #nss_base_rpcou=Rpc,dc=example,dc=com?one #nss_base_ethersou=Ethers,dc=example,dc=com?one #nss_base_netmasksou=Networks,dc=example,dc=com?ne #nss_base_bootparamsou=Ethers,dc=example,dc=com?one #nss_base_aliasesou=Aliases,dc=example,dc=com?one #nss_base_netgroupou=Netgroup,dc=example,dc=com?one # Just assume that there are no supplemental groups for these named users nss_initgroups_ignoreusers root,ldap,named,avahi,haldaemon,dbus,radvd,tomcat,radiusd,news,mailman,nscd,gdm,polkituser # attribute/objectclass mapping # Syntax: #nss_map_attributerfc2307attributemapped_attribute #nss_map_objectclassrfc2307objectclassmapped_objectclass # configure --enable-nds is no longer supported. # NDS mappings #nss_map_attribute uniqueMember member # Services for UNIX 3.5 mappings #nss_map_objectclass posixAccount User #nss_map_objectclass shadowAccount User #nss_map_attribute uid msSFU30Name #nss_map_attribute uniqueMember msSFU30PosixMember #nss_map_attribute userPassword msSFU30Password #nss_map_attribute homeDirectory msSFU30HomeDirectory #nss_map_attribute homeDirectory msSFUHomeDirectory #nss_map_objectclass posixGroup Group #pam_login_attribute msSFU30Name #pam_filter objectclass=User #pam_password ad # configure --enable-mssfu-schema is no longer supported. # Services for UNIX 2.0 mappings #nss_map_objectclass posixAccount User #nss_map_objectclass shadowAccount user #nss_map_attribute uid msSFUName #nss_map_attribute uniqueMember posixMember #nss_map_attribute userPassword msSFUPassword #nss_map_attribute homeDirectory msSFUHomeDirectory #nss_map_attribute shadowLastChange pwdLastSet #nss_map_objectclass posixGroup Group #nss_map_attribute cn msSFUName #pam_login_attribute msSFUName #pam_filter objectclass=User #pam_password ad # RFC 2307 (AD) mappings #nss_map_objectclass posixAccount user #nss_map_objectclass shadowAccount user #nss_map_attribute uid sAMAccountName #nss_map_attribute homeDirectory unixHomeDirectory #nss_map_attribute shadowLastChange pwdLastSet #nss_map_objectclass posixGroup group #nss_map_attribute uniqueMember member #pam_login_attribute sAMAccountName #pam_filter objectclass=User #pam_password ad # configure --enable-authpassword is no longer supported # AuthPassword mappings #nss_map_attribute userPassword authPassword # AIX SecureWay mappings #nss_map_objectclass posixAccount aixAccount #nss_base_passwd ou=aixaccount,?one #nss_map_attribute uid userName #nss_map_attribute gidNumber gid #nss_map_attribute uidNumber uid #nss_map_attribute userPassword passwordChar #nss_map_objectclass posixGroup aixAccessGroup #nss_base_group ou=aixgroup,?one #nss_map_attribute cn groupName #nss_map_attribute uniqueMember member #pam_login_attribute userName #pam_filter objectclass=aixAccount #pam_password clear # Netscape SDK LDAPS #ssl on # Netscape SDK SSL options #sslpath /etc/ssl/certs # OpenLDAP SSL mechanism # start_tls mechanism uses the normal LDAP port, LDAPS typically 636 #ssl start_tls #ssl on # OpenLDAP SSL options # Require and verify server certificate (yes/no) # Default is to use libldap's default behavior, which can be configured in # /etc/openldap/ldap.conf using the TLS_REQCERT setting. The default for # OpenLDAP 2.0 and earlier is "no", for 2.1 and later is "yes". #tls_checkpeer yes # CA certificates for server certificate verification # At least one of these are required if tls_checkpeer is "yes" #tls_cacertfile /etc/ssl/ca.cert #tls_cacertdir /etc/ssl/certs # Seed the PRNG if /dev/urandom is not provided #tls_randfile /var/run/egd-pool # SSL cipher suite # See man ciphers for syntax #tls_ciphers TLSv1 # Client certificate and key # Use these, if your server requires client authentication. #tls_cert #tls_key # Disable SASL security layers. This is needed for AD. #sasl_secprops maxssf=0 # Override the default Kerberos ticket cache location. #krb5_ccname FILE:/etc/.ldapcache # SASL mechanism for PAM authentication - use is experimental # at present and does not support password policy control #pam_sasl_mech DIGEST-MD5 uri ldap://127.0.0.1/ ssl no tls_cacertdir /etc/openldap/cacerts pam_password md5 base.ldif # create new dn: dc=primecorp,dc=com objectClass: dcObject objectClass: organization o: primecorp Organization dc: primecorp dn: cn=Manager,dc=primecorp,dc=com objectClass: organizationalRole cn: manager dn: ou=People,dc=primecorp,dc=com objectClass: organizationalUnit ou: People dn: ou=Group,dc=primecorp,dc=com objectClass: organizationalUnit ou: Group ldapsearch -x -h 10.127.1.146 -b "dc=primecorp,dc=com" -D 'admin(a)primecorp.com' -W "cn=admin" Enter LDAP Password: ldap_bind: Invalid DN syntax (34) additional info: invalid DN I have installed and the installation went fine. but ldapsearch keeps giving the same error i also tried other combinations on the dn like adding a ou=Peopledc=primecorp,dc=com, many other combinations but i stll kept hitting the same error or "invalid credentials". I completley stuck as to whether i am putting the correct information.I am not able to see what is exactly wrong with the config. I am using Fedora Core 11 by the way. If someone could please help me with this i would be so appreciative, LDAP looks so easy to set up yet there is something probably so small preventing it being set up correctly. if you need any more information on this just ask me. Regards Joseph

3 2

bind using CN instead of UID
by Craig White 07 Oct '11

07 Oct '11

Obviously there is something that I don't understand because I would expect to be able to bind using CN as well as UID attribute... version: 2.4.21-0ubuntu5.5 ***** this as you can see works ***** # ldapsearch -x -D 'uid=cwhite,ou=people,dc=ttinet,dc=local' -W '(uid=cwhite)' uid, cn Enter LDAP Password: # extended LDIF # # LDAPv3 # base <dc=ttinet,dc=local> (default) with scope subtree # filter: (uid=cwhite) # requesting: uid, cn # # cwhite, people, ttinet.local dn: uid=cwhite,ou=people,dc=ttinet,dc=local cn: Craig White # search result search: 2 result: 0 Success # numResponses: 2 # numEntries: 1 ***** same as above but using cn instead of uid ***** # ldapsearch -x -D 'cn=Craig White,ou=people,dc=ttinet,dc=local' -W '(uid=cwhite)' uid, cn Enter LDAP Password: ldap_bind: Invalid credentials (49) I have to believe that if this is an ACL issue, then the very first rule is the problem... olcAccess: {0}to attrs=userPassword,shadowLastChange by dn.exact="uid=administ rator,ou=people,dc=ttinet,dc=local" write by self write by anonymous auth by * none What is it that I am missing? -- Craig White ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ craig.white(a)ttiltd.com 1.800.869.6908 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ www.ttiassessments.com Need help communicating between generations at work to achieve your desired success? Let us help!

4 4

Patching openldap?
by NetNinja 07 Oct '11

07 Oct '11

Hello, I have been reading up on OpenLDAP. I have installed it on RHEL 5.5 but I have seen documention saying that openldap needs to be patched to work with Solaris. Can someone tell me if this still the case and if so where to get the patch. If not any info you can provide wold be great. Thanks

4 3

Re: Ldap logs accounting
by Hugo Deprez 07 Oct '11

07 Oct '11

Hello, thank you that was exactly what I was looking for. Does anyone know a software such as a web interface, which will be able to read the data from the accesslog base and display them in a more friendly way ? Regards, Hugo On 6 October 2011 04:55, Quanah Gibson-Mount <quanah(a)zimbra.com> wrote: > --On Wednesday, October 05, 2011 11:41 AM +0200 Hugo Deprez > <hugo.deprez(a)gmail.com> wrote: > >> Dear community, >> >> I am currently using openldap 2.4.23-3 on Debian Lenny. I need to be >> able to log all the change made on the directory. >> For exemple if a account is delete I would like to log who did it and >> at what time. >> I want to do some accounting. >> >> Do you know how I could do that ? I didn't found anything on google. > > man slapo-accesslog > > --Quanah > > -- > > Quanah Gibson-Mount > Sr. Member of Technical Staff > Zimbra, Inc > A Division of VMware, Inc. > -------------------- > Zimbra :: the leader in open source messaging and collaboration >

3 4

Re: Unable to create home directory (LDAP Authentication)
by vijay s sheelavantar 07 Oct '11

07 Oct '11

Hi,I am sorry for the inconvenience caused due to the unreadable format. On fedora I don't have this file. /etc/pam.d/common-session. Below logs for your reference. in the log file /var/log/messages i found the following error Oct  6 13:37:56 localhost setroubleshoot: SELinux is preventing sshd (sshd_t) "write" to ./home (home_root_t). For complete SELinux messages. run sealert -l ecdf3def-df6e-4d5b-851b-4e9bf155e57d and in the log file /var/log/secure below error found. Oct  6 15:14:04 localhost sshd[3844]: pam_unix(sshd:session): session closed for user kimOct  6 15:14:07 localhost sshd[3900]: Accepted password for kim from 10.254.194.148 port 57079 ssh2Oct  6 15:14:07 localhost sshd[3900]: pam_mkhomedir(sshd:session): unable to create directory /home/kim: Permission deniedOct  6 15:14:07 localhost sshd[3900]: pam_unix(sshd:session): session opened for user kim by (uid=0)Oct  6 15:14:07 localhost sshd[3900]: error: ssh_selinux_setup_pty: security_compute_relabel: Invalid argument please help me to find a solution. Warm Regards,Vijay S.

2 1

Not getting Password expiry message
by pradyumna dash 07 Oct '11

07 Oct '11

Hi, I have setted up ppolicy schema for password handling, its working fine except am not getting the password expiry message. Is it a known issue or am doing something wrong. am using OpenLDAP 2.4 on SLES 11 SP1 Please suggest. Regards, Neo

3 3

LDAP + Winbind + Windows Domain
by Dana, Eric 06 Oct '11

06 Oct '11

I have a Linux server configured as a domain member of a Windows domain using Winbind. I want to use the server to: 1. Maintain GID/UID definitions for Linux <-> Windows domain mapping. 2. Serve Linux file shares. 3. Handle LDAP requests for id mappings (see #1) and LDAP information from the master LDAP server (Windows domain controller). 4. Authenticate users using the password on the Windows DC. I'm trying to find the best way to setup LDAP on the Linux server to handle issues #1 and #3. Issues #4 is working using Winbind. I cannot change/add configuration/program on the Windows LDAP (DC) server. This LDAP server would primarily be used by other Linux machines. I've seen suggestions using proxy and/or referrals, would like some more clarity on the best approach. Thanks. Eric Dana

1 0

OATH HOTP authentication with OpenLDAP
by Dimitri 05 Oct '11

05 Oct '11

Hi, For a long time our company has been planning to implement one-time password authentication as a LDAP SIMPLE auth mechanism. The goal behind that is to enable unified OTP authentication for a wide range of server applications that are capable of LDAP SIMPLE auth. The list of most important applications includes (but is not limited too): a Dovecot IMAP + RoundCube tandem; third-party JavaEE applications, like Atlassian Confluence and JIRA; in-house web-applications; etc. OATH HOTP [1] has been chosen as the actual OTP mechanism, due to its openness and wide availability of cheap hardware HOTP-compliant tokens, as well as software "tokens" for mobile phones. Implementing OTP on a LDAP server side will not only provide unified OTP auth, but also will allow to centralize authentication-related information (user database + token database) and will let us benefit from OpenLDAP out-of-the box features like replication. Right now we are entering the actual implementation phase, and I will be very glad to hear general architectural considerations as well as answers to my questions that already arose. 1. We have chosen to use SLAPI, not overlay API, to make our authentication plugin portable to other LDAP servers; but still our main target is OpenLDAP and we're not going to migrate to any other LDAP server (but our clients might). In terms of SLAPI, this will be a "preoperation bind plugin". If somebody thinks our choice is awfully bad, please don't hesitate to share your considerations. 2. Another reason for choosing SLAPI was much clearer API and, most importantly, availability of simple, synchronous functions for performing internal operations (searches, modifications). It seemed to me that overlay API provides only complex, callback-based functions for internal operations. Please let me know if I've overlooked that in the documentation (or, better say, source code, since overlay API is actually undocumented, opposite to SLAPI [2]). 3. Current state of SLAPI support in OpenLDAP completely lacks functions like slapi_is_root_suffix(), slapi_dn_isroot(), as well as the whole slapi_be_* function family. This makes impossible to determine root DN for authenticating principal. If we decide to actually implement those functions, what is the preferred way to submit the code to mainstream? To open an ITS issue and attach a patch to it? 4. For SLAPI plugins, is there a preferred way of obtaining plugin configuration, other than parsing ARGV? I know that in RedHat Directory server plugins often use their corresponding cn=plugins,cn=config entries to store config, but what about OpenLDAP? 5. HOTP algorithm uses SHA1 cryptographic hash. We clearly understand that if using SLAPI we won't be able to use OpenLDAP SHA1 implementation available via lutil_sha1.h. In order not to implement SHA1 ourselves, is it okay to introduce a dependency on OpenSSL/GnuTLS/NSS? For example, two RedHat plugins from their distribution (namely "http" and "pwdstorage" [3]) do use NSS and hence include ssl.h. 6. We decided to store token information in its dedicated subtree, like "ou=Tokens,dc=example,dc=com" (configurable). Each token will have its own entry that will store its serial number, seed, counter, PIN and its current owner (a single DN of user that this token has been assigned to), thus introducing a many-to-one relationship between tokens and users. Entries with absent "owner" attribute will form a pool of tokens available for assignment. Token synchronization (computing actual counter value from two successive passwords) will be implemented as an extended operation. A preliminary version of schema is available and we can publish it right now for review. Again, if there are any considerations and/or critical remarks, don't hesitate to share them. That's all for the first post; I beg my pardon for a long and verbose text. We will be very thankful for any feedback on the topic. Thanks! Dimitri CargoSoft LLC, Russia [1] OATH HOTP: http://tools.ietf.org/html/rfc4226 [2] RedHat Directory Server Plugin Guide: http://docs.redhat.com/docs/en-US/Red_Hat_Directory_Server/8.2/html/Plug-in… [3] http://git.fedorahosted.org/git/?p=389/ds.git;a=tree;f=ldap/servers/plugins…

3 2

Installation Problem with BDB 4.8
by Rajeshwar Bharathi 05 Oct '11

05 Oct '11

All, I am trying to install Open LDAP 2.4.23 with Berkley DB v4.8. I am getting errors with the BDB version etc My Server is a: *CentOS release 5.6 (Final)* *2.6.18-238.19.1.el5 x86_64 GNU/Linux* The system already has older versions od BDB installed already on it. [root@myserver]# rpm -qa|grep db4 db4-4.3.29-10.el5_5.2 db4-4.3.29-10.el5_5.2 db4-devel-4.3.29-10.el5_5.2 db4-devel-4.3.29-10.el5_5.2 To use the newly installed/supported BDB 4.8 version I use the environment flags with my consfigure and make commands Step 1: $env CPPFLAGS="-I/usr/local/BerkeleyDB.4.8/include/"LDFLAGS="-L/usr/local/BerkeleyDB.4.8/lib" ./configure Step 2: $make depend Step 3: $make Step 1-3 goes thru fine At Step 4: when I run make install $make install I get the fol erros towards the end. make[3]: Entering directory `/u001/projects/cyrusIMAP/openldap-2.4.23/servers/slapd/back-bdb' /bin/sh ../../../libtool --tag=disable-shared --mode=compile cc -g -O2 -I../../../include -I../../../include -I.. -I./.. -I/usr/local/BerkeleyDB.4.8/include/LDFLAGS=-L/usr/local/BerkeleyDB.4.8/lib -c init.c cc -g -O2 -I../../../include -I../../../include -I.. -I./.. -I/usr/local/BerkeleyDB.4.8/include/LDFLAGS=-L/usr/local/BerkeleyDB.4.8/lib -c init.c -o init.o init.c: In function 'bdb_db_open': init.c:532: error: 'DB_READ_COMMITTED' undeclared (first use in this function) init.c:532: error: (Each undeclared identifier is reported only once init.c:532: error: for each function it appears in.) make[3]: *** [init.lo] Error 1 make[3]: Leaving directory `/u001/projects/cyrusIMAP/openldap-2.4.23/servers/slapd/back-bdb' make[2]: *** [.backend] Error 1 make[2]: Leaving directory `/u001/projects/cyrusIMAP/openldap-2.4.23/servers/slapd' make[1]: *** [all-common] Error 1 make[1]: Leaving directory `/u001/projects/cyrusIMAP/openldap-2.4.23/servers' make: *** [all-common] Error 1 Can anyone please let me know why the init.c program is unable to open the bdb. Any help would be appreciated. -- Rajeshwar BM Bangalore INDIA

2 1

Ldap logs accounting
by Hugo Deprez 05 Oct '11

05 Oct '11

Dear community, I am currently using openldap 2.4.23-3 on Debian Lenny. I need to be able to log all the change made on the directory. For exemple if a account is delete I would like to log who did it and at what time. I want to do some accounting. Do you know how I could do that ? I didn't found anything on google. Regards, Hugo

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