openldap-technical

openldap-technical@openldap.org

7 participants
9901 discussions

rfc2307bis.schema woes (OpenIndiana 151a7 client)
by Tobias Verbeke 10 Apr '13

10 Apr '13

Dear list, I am trying to add an OpenIndiana 151a7 machine as an LDAP client of an Ubuntu 12.04.1 server with slapd version as shipped with it: # slapd -V @(#) $OpenLDAP: slapd (Oct 17 2012 19:48:41) $ buildd@komainu:/build/buildd/openldap-2.4.28/debian/build/servers/slapd On the OI client I get # ldapclient init machine.openanalytics.eu Can not find the nisDomainObject for domain Google found out for me that the OpenIndiana LDAP client assumes the rfc2307bis.schema to be used instead of the nis.schema that is used by default and grep confirms the nisDomainObject can be found there: # grep -nr nisDomain* /etc/ldap/schema. ./rfc2307bis.schema:158:attributetype ( 1.3.6.1.1.1.1.30 NAME 'nisDomain' ./rfc2307bis.schema:269:objectclass ( 1.3.6.1.1.1.2.15 NAME 'nisDomainObject' SUP top AUXILIARY ./rfc2307bis.schema:271: MUST nisDomain ) To make it a little bit simpler for the newbie I am, I made sure static configuration is used (by removing /etc/ldap/slapd.d) The relevant part of the slapd.conf now reads # Schema and objectClass definitions include /etc/ldap/schema/core.schema include /etc/ldap/schema/cosine.schema include /etc/ldap/schema/rfc2307bis.schema include /etc/ldap/schema/ldapns.schema include /etc/ldap/schema/inetorgperson.schema When running slaptest, I get # slaptest 51655577 /etc/ldap/schema/rfc2307bis.schema: line 5 attributetype: Duplicate attributeType: "1.3.6.1.1.1.1.0" slaptest: bad configuration file! However, when grepping on "1.3.6.1.1.1.1.0", I only get the rfc2307bis.schema file: # grep -rn 1.3.6.1.1.1.1.0 /etc/ldap/schema /etc/ldap/schema/rfc2307bis.schema:1:attributetype ( 1.3.6.1.1.1.1.0 NAME 'uidNumber' Where else can this attributeType live? Can I provide more information? I am a bit puzzled, so many thanks in advance for any pointer! Best, Tobias

1 0

Re: How to improve performance with MDB backend?
by Saša-Stjepan Bakša 09 Apr '13

09 Apr '13

I am sorry replaying directly. I didn't check who was in TO field. OK I will try Re24. Tnx again. Sasa On Tue, Apr 9, 2013 at 4:15 PM, Quanah Gibson-Mount <quanah(a)zimbra.com>wrote: > --On Tuesday, April 09, 2013 2:07 PM +0200 Saša-Stjepan Bakša < > ssbaksa(a)gmail.com> wrote: > > >> >> Tnx. I will add what you suggest and try to run modify test with that. I >> didn't done that already because my mdb database is overflowed. I have >> set it to 100GB but it wasn't enough. I am not sure why. Are there logs >> inside? I have 1 mil users but they didn't use all data storage. Hmmm, >> maybe indexes, I have 8 of them. I know how to look for hdb/bdb problems >> but mdb is a puzzle for me (for now). >> > > Please keep replies to the list. I would suggest you try current OpenLDAP > RE24, there was a growth issue fixed since the 2.4.35 release (ITS#7565). > > > --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 >

1 0

openLDAP storing passwords in plain text
by Derryl Varghese 09 Apr '13

09 Apr '13

I am setting up openLDAP for one of my Java applications. Usernames and passwords are stored in openLDAP and users are able to update their passwords via the application (using the javax.naming.directory API'). I imported our users from our existing Sun Directory Server into openLDAP. Import was successfull and passwords were encrypted in SSHA format. I noticed that when i update a password from the application, it stores it in 'Plain Text' format. I can unhide the password when i view it via Apache Directory Studio. A lot of googling later, i tried setting the "password-hash {SSHA}" in the slapd.conf file and that didn't help me either. I am on a windows environment. I am passing the password to openLDAP in plain text format. There is no encryption going on in the code. I know i can encrypt it in the application but i would prefer openLDAP to do it for me. Please let me know if i can do anything on the openLDAP side. This is the JAVA code i use today to modify passwords. This has been working fine in our existing environment for the past 7 years. ModificationItem[] newAttribs = new ModificationItem[1]; Attribute passwordAttrib = new BasicAttribute(DirectoryConstants.USER_PASSWORD, password); ModificationItem passwordItem = new ModificationItem(DirContext.REPLACE_ATTRIBUTE, passwordAttrib); newAttribs[0] = passwordItem; ..... DirContext ctx = this.getContext(); ctx.modifyAttributes( DirectoryConstants.USER_UID + "=" + userId + "," + ou, newAttribs);

4 4

Trouble getting ppolicy overlay to work
by D C 09 Apr '13

09 Apr '13

I'm really banging my head trying to get the ppolicy overlay to work properly. My only indication that I am partially on the right track is that if I set pwdSafeModify=TRUE in my default policy, then I get the following error from pam_ldap when changing my password. If I set it back to false, then I can change my password. LDAP password information update failed: Insufficient access Must supply old password to be changed as well as new one passwd: Authentication token manipulation error However, everything else in the policy is being ignored. any help would be greatly appreciated. Thanks! * I am assuming that the password policy is going to be enforced by ldap, so testing with pam_ldap is not necessary at this point. I should be able to use any client such as apache directory studio to test password policy. Version Info: CentOS 6.4 CentOS packaged openldap-servers-2.4.23 slapd.conf: # ( I am aware that I have * write. this is just for desperate testing on a test box ) 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/sudo.schema include /etc/openldap/schema/pwm.schema include /etc/openldap/schema/ppolicy.schema moduleload ppolicy.la moduleload syncprov.la # Allow LDAPv2 client connections. This is NOT the default. allow bind_v2 pidfile /var/run/openldap/slapd.pid argsfile /var/run/openldap/slapd.args ####################################################################### # ACL ####################################################################### access to attrs=userPassword,pwmResponseSet,pwmToken by dn="uid=root,ou=People,dc=example,dc=net" write by dn="cn=svc_pam,ou=SVC_Accounts,dc=example,dc=net" write by dn="cn=svc_pwm,ou=SVC_Accounts,dc=example,dc=net" write by dn="cn=replica,dc=example,dc=net" read by anonymous auth by self write by * none access to * by self write by * write ####################################################################### # ldbm and/or bdb database definitions ####################################################################### database bdb suffix "dc=example,dc=net" rootdn "cn=admin,dc=example,dc=net" rootpw {SMD5}********* overlay ppolicy ppolicy_default "cn=default,ou=policies,dc=example,dc=net" ppolicy_use_lockout overlay syncprov syncprov-checkpoint 100 10 directory /var/lib/ldap loglevel 65535 # 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 index contextCSN eq index sudoUser eq index entryCSN eq index entryUUID eq # default, policies, example.net dn: cn=default,ou=policies,dc=example,dc=net objectClass: top objectClass: person objectClass: pwdPolicy cn: default sn: default policy pwdAttribute: userPassword pwdMaxAge: 7776002 pwdExpireWarning: 432000 pwdInHistory: 3 pwdLockout: TRUE pwdGraceAuthNLimit: 0 pwdMustChange: TRUE pwdAllowUserChange: TRUE pwdLockoutDuration: 45 pwdMaxFailure: 2 pwdFailureCountInterval: 1 pwdMinLength: 12 pwdCheckQuality: 1 pwdSafeModify: TRUE

1 0

Re: How to improve performance with MDB backend?
by Quanah Gibson-Mount 09 Apr '13

09 Apr '13

--On Tuesday, April 09, 2013 2:07 PM +0200 Saša-Stjepan Bakša <ssbaksa(a)gmail.com> wrote: > > > Tnx. I will add what you suggest and try to run modify test with that. I > didn't done that already because my mdb database is overflowed. I have > set it to 100GB but it wasn't enough. I am not sure why. Are there logs > inside? I have 1 mil users but they didn't use all data storage. Hmmm, > maybe indexes, I have 8 of them. I know how to look for hdb/bdb problems > but mdb is a puzzle for me (for now). Please keep replies to the list. I would suggest you try current OpenLDAP RE24, there was a growth issue fixed since the 2.4.35 release (ITS#7565). --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

1 0

Remote access to the directory schema
by Rick van Rein (OpenFortress) 08 Apr '13

08 Apr '13

Hello, Do I understand correctly, is the schema of a directory always accessible to its remote users? Because when I request | ldapsearch -x -h ldap.example.com -b dc=example,dc=com subschemaSubentry I get entries like | dn: dc=example,dc=com | subschemaSubentry: cn=Subschema | | dn: cn=someone,dc=example,dc=com | subschemaSubentry: cn=Subschema but when I then try things like | ldapsearch -x -h ldap.example.com -b dc=example,dc=com -E subentries=true cn=Subschema I get no results. How should this work? Do schema entries have to be explicitly enabled in the ACL as though they were normal entries, or is the schema always visible? Thanks, -Rick

3 4

~Bob Fitch~
by Bob Fitch 08 Apr '13

08 Apr '13

http://www.rouviere-bat.com/htteopa/5875137920578718644.8901773532214087666… Bob Fitch

1 0

How to improve performance with MDB backend?
by Saša-Stjepan Bakša 08 Apr '13

08 Apr '13

Hi, Maybe this is not the best way to ask but I would like to get some performance expectations or maybe suggestions how to improve performance. I do have relatively long experience with OpenLDAP as a precompiled package and with much less users so performance was not an issue for those installations. Now I need to put few million users (now one million for test), custom tailored schema and search performance is crucial but also modify performance is big issue. Before MDB I have used HDB as backend. What to do to improve write part of performance or performance in general (when adding data – from time to time – OpenLDAP stalls in a way)? Just around 5 add/mod operations during that time then it continue with much higher speed. I have used many different sources to find out other peoples experience and I didn’t choose to write to list lightly but I really need some help/hints. As a hardware I am using two ProLiant DL360p Gen8 servers with: 48GB RAM, HP Smart Array P420i Controller, 2 x EG0600FBDSR 558 GB hard disk in RAID 1. 2 Ethernet ports are bonded to achieve redundancy and performance and connected to Cisco 3750 switch OS is Ubuntu 12.04.2 LTS server with no unnecessary daemons installed. Disk is partitioned this way. Filesystem Size Used Avail Use% Mounted on /dev/sda1 46G 1.4G 43G 4% / udev 24G 4.0K 24G 1% /dev tmpfs 9.5G 240K 9.5G 1% /run none 5.0M 0 5.0M 0% /run/lock none 24G 0 24G 0% /run/shm /dev/sda3 232G 32G 189G 15% /var /dev/sda4 230G 2.4G 216G 2% /opt OpenLDAP is latest one – 2.4.35 compiled on Ubuntu server with addition of Berkley db 5.3.21 (I am not using it but …) and no special switches are used during configuration except the on which puts installation to /opt/openldap directory. I am using also libhoard.so as a memory manager (latest one downloaded from HOARD web site). OpenLDAP is configured as MultiMaster N Way and I am using MDB as backend database. Config is in conf.d stile. root@spr1:~# more /opt/openldap/etc/openldap/slapd.d/cn\=config.ldif # AUTO-GENERATED FILE - DO NOT EDIT!! Use ldapmodify. # CRC32 47664f80 dn: cn=config objectClass: olcGlobal cn: config olcArgsFile: /var/run/slapd/slapd.args olcLogLevel: none olcPidFile: /var/run/slapd/slapd.pid structuralObjectClass: olcGlobal creatorsName: cn=config entryUUID: a8df00ce-80fb-1031-8652-fff9cf1d6a3e createTimestamp: 20120822232009Z olcServerID: 1 ldap://spr1.lab.os olcServerID: 2 ldap://spr2.lab.os olcIdleTimeout: 5 olcThreads: 6 entryCSN: 20130404141239.680528Z#000000#001#000000 modifiersName: cn=admin,cn=config modifyTimestamp: 20130404141239Z contextCSN: 20130404141404.368953Z#000000#001#000000 contextCSN: 20130329141804.133907Z#000000#002#000000 And database: root@spr1:~# more /opt/openldap/etc/openldap/slapd.d/cn\=config/olcDatabase={1}mdb.ldif # AUTO-GENERATED FILE - DO NOT EDIT!! Use ldapmodify. # CRC32 405c8aaf dn: olcDatabase={1}mdb objectClass: olcDatabaseConfig objectClass: olcMdbConfig olcDatabase: {1}mdb olcDbDirectory: /var/lib/ldap olcSuffix: dc=spr olcAccess: {0}to attrs=userPassword,shadowLastChange by self write by anonymou s auth by dn="cn=admin,dc=spr" write by * none olcAccess: {1}to attrs=shadowLastChange by self write by * read olcAccess: {2}to dn.base="" by * read olcAccess: {3}to * by self write by dn="cn=admin,dc=spr" write by * read olcLastMod: TRUE olcRootDN: cn=admin,dc=spr olcRootPW:: e1NTSEF9eDRVRTBiV2Z4YnFSNnZDVDdKRWEwSWRhWFRhMDN2M3I= olcDbNoSync: TRUE olcDbMaxSize: 107374182400 structuralObjectClass: olcMdbConfig entryUUID: 804a8ede-2cc3-1032-9b7a-c7b2eb845e03 creatorsName: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth createTimestamp: 20130329135129Z olcDbIndex: objectClass eq olcDbIndex: uid eq olcDbIndex: MSISDN eq olcDbIndex: IMSI eq olcDbIndex: pfUsername eq olcDbIndex: entryCSN eq olcDbIndex: entryUUID eq olcDbIndex: contextCSN eq olcMirrorMode: TRUE olcSyncrepl: {0}rid=003 provider=ldap://spr1.lab.os binddn="cn=admin,dc=spr" b indmethod=simple credentials=siemens searchbase="dc=spr" type=refreshOnly int erval=00:00:00:10 retry="5 5 300 5" timeout=1 olcSyncrepl: {1}rid=004 provider=ldap://spr2.lab.os binddn="cn=admin,dc=spr" b indmethod=simple credentials=siemens searchbase="dc=spr" type=refreshOnly int erval=00:00:00:10 retry="5 5 300 5" timeout=1 olcDbCheckpoint: 8192 15 entryCSN: 20130404141404.368953Z#000000#001#000000 modifiersName: cn=admin,cn=config modifyTimestamp: 20130404141404Z This is output from iotop during ldapmodify test (1 mil user, two clients modifying each user in sequence , 1 DN / 1 attribute per user): Total DISK READ: 0.00 B/s | Total DISK WRITE: 15.30 M/s TID PRIO USER DISK READ DISK WRITE SWAPIN IO> COMMAND 4403 be/4 root 0.00 B/s 0.00 B/s 0.00 % 98.88 % [flush-8:0] 4838 be/4 openldap 0.00 B/s 3.41 M/s 0.00 % 21.68 % slapd -h ldap:/// -F /opt/openldap/etc/~ldap/slapd.d -g openldap -u openldap -4 4837 be/4 openldap 0.00 B/s 3.19 M/s 0.00 % 19.13 % slapd -h ldap:/// -F /opt/openldap/etc/~ldap/slapd.d -g openldap -u openldap -4 4836 be/4 openldap 0.00 B/s 2.83 M/s 0.00 % 17.48 % slapd -h ldap:/// -F /opt/openldap/etc/~ldap/slapd.d -g openldap -u openldap -4 10889 be/4 openldap 0.00 B/s 2.94 M/s 0.00 % 16.30 % slapd -h ldap:/// -F /opt/openldap/etc/~ldap/slapd.d -g openldap -u openldap -4 10962 be/4 openldap 0.00 B/s 2.92 M/s 0.00 % 15.25 % slapd -h ldap:/// -F /opt/openldap/etc/~ldap/slapd.d -g openldap -u openldap -4 1816 be/3 root 0.00 B/s 0.00 B/s 0.00 % 3.23 % [jbd2/sda3-8] And top: top - 11:56:27 up 4 days, 1:43, 1 user, load average: 2.71, 2.88, 3.19 Tasks: 224 total, 1 running, 223 sleeping, 0 stopped, 0 zombie Cpu(s): 2.6%us, 0.1%sy, 0.0%ni, 91.3%id, 6.0%wa, 0.0%hi, 0.0%si, 0.0%st Mem: 49424228k total, 35362892k used, 14061336k free, 127844k buffers Swap: 46874876k total, 0k used, 46874876k free, 32631568k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 4833 openldap 20 0 101g 30g 29g S 91 64.1 196:30.20 slapd 4403 root 20 0 0 0 0 D 2 0.0 2:41.89 flush-8:0 1 root 20 0 24472 2444 1360 S 0 0.0 0:04.36 init 2 root 20 0 0 0 0 S 0 0.0 0:00.03 kthreadd 3 root 20 0 0 0 0 S 0 0.0 0:00.37 ksoftirqd/0

3 2

Loosing existing entries when implementing syncrepl N-Way Multi-Master Replication (openldap-2.4.32)
by Joe Phan 07 Apr '13

07 Apr '13

Hi, I have some general questions related to syncrepl N-Way Multi-Master Replication (openldap-2.4.32 on Solaris 10). I already configured a LDAP server and added user entries to DIT. From a client machine, I am able to retrieve user entries via ldapsearch, and login using LDAP user entries is also successful. When I try to configure the LDAP server to be syncrepl N-Way Multi-Master Replication - Server1, existing entries in DIT are gone. From the client machine, ldapsearch command returns empty. - For existing entries in DIT, can we keep them when implementing syncrepl N-Way Multi-Master Replication or we must create them again from the beginning? Regards, Joe

2 1

Re: Anonymous Bind ACL Problems
by Shawn Morford 06 Apr '13

06 Apr '13

On Fri, Apr 5, 2013 at 1:11 PM, Quanah Gibson-Mount <quanah(a)zimbra.com>wrote: > --On Friday, April 05, 2013 12:46 PM -0700 Dark Morford < > darkmorford+ldap(a)gmail.com> wrote: > > I'm setting up my first LDAP server; just using it as an auth provider >> for Apache until I'm more comfortable with things. I was able to get it >> up and running with a few user entries, but I can't get anonymous >> searching to work the way I want. >> >> It's configured (cn=config) style, and the ACLs are: >> {0}to attrs=uid by anonymous read by users read >> {1}to attrs=userPassword by anonymous auth by self write >> {2}to * by users read >> > > access to entry by * read needs to be in there too before {2}. > > --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 > Adding the access entry exactly like you have it gave me an error; I managed to figure out that it needed to be 'to attrs=entry by * read'. And now it seems to be working, so thanks for that. I'm not sure I understand why it's necessary, though. The client service (Apache) just needs to find out if a particular uid exists. Why does it need access to the whole entry?

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openldap-technical