openldap-technical

openldap-technical@openldap.org

7 participants
9901 discussions

Re: ldap_add: Server is unwilling to perform (53) error:
by vinodh kumar 17 Mar '08

17 Mar '08

On Mon, Mar 17, 2008 at 11:29 PM, Quanah Gibson-Mount <quanah(a)zimbra.com> wrote: > --On Monday, March 17, 2008 11:26 PM +0530 vinodh kumar <vinstce(a)gmail.com > > > wrote: > > our ldif file is, > > > > > > > > dn: cn:new,dc=example,dc=com > > > > objectClass:posixAccount > > cn:new > > uid:new > > displayname:neww > > homedirectory > > > homedirectory:/home/new > > I suggest you research into objectClasses and valid objectClass chains. > The error you've gotten is quite correct, you've failed to provide a > structural objectClass in your entry. Think of it in terms of object > oriented programming -- Every entry object must be of a specific class, > which can then be added onto with auxiliary information. posixAccount is > auxiliary, you need to add a valid structural OC to your entry. > > "account" may be the one you're looking for: oh thanks:) actually i have a doubt that where to add this??? objectclass ( 0.9.2342.19200300.100.4.5 NAME 'account' > SUP top STRUCTURAL > MUST userid > MAY ( description $ seeAlso $ localityName $ > organizationName $ organizationalUnitName $ host ) > ) > > > --Quanah > > so , we need to add a entry objectclass : account in our .ldif file right??? and do i need to add the above in schema file ???? sorry if my doubt is silly!! bare with me :) -- regards vinodh i blog @ http://vinsvision.wordpress.com

2 1

ldap_add: Server is unwilling to perform (53) error:
by vinodh kumar 17 Mar '08

17 Mar '08

hello all, we are trying to setup a ldap server which uses the mysql as back-end instead of bdb backend.we have installed slapd and ldap-utils in debian-etch .we also have installed mylibodbc, mysql-client-5,mysql-server-5. we have established the mysql-ODBC connectivity and tested the connectivity using isql.we have configured the slapd.conf file to connect mysql and when we tried to add entries using ldapadd , we get the following err ldap_add: Server is unwilling to perform (53) additional info: operation not permitted within namingContext this is the slapd.conf file # This is the main slapd configuration file. See slapd.conf(5) for more # info on the configuration options. ############################# Global Directives: # Features to permit #allow bind_v2 # Schema and objectClass definitions include /etc/ldap/schema/core.schema include /etc/ldap/schema/cosine.schema include /etc/ldap/schema/nis.schema include /etc/ldap/schema/inetorgperson.schema # Where the pid file is put. The init.d script # will not stop the server if you change this. pidfile /var/run/slapd/slapd.pid # List of arguments that were passed to the server argsfile /var/run/slapd/slapd.args # Read slapd.conf(5) for possible values loglevel 0 # Where the dynamically loaded modules are stored modulepath /usr/lib/ldap moduleload back_sql # The maximum number of entries that is returned for a search operation sizelimit 500 # The tool-threads parameter sets the actual amount of cpu's that is used # for indexing. tool-threads 1 ############################## > > ######################################### > # Specific Backend Directives for bdb: > # Backend specific directives apply to this backend until another > # 'backend' directive occurs > backend sql > checkpoint 512 30 > > ####################################################################### > # Specific Backend Directives for 'other': > # Backend specific directives apply to this backend until another > # 'backend' directive occurs > #backend <other> > > ####################################################################### > # Specific Directives for database #1, of type bdb: > # Database specific directives apply to this databasse until another > # 'database' directive occurs > database sql > suffix "dc=example,dc=org" > rootdn "cn=admin,dc=example,dc=org" > rootpw ldap > dbname ldap > dbuser new > dbpasswd new > #insentry_query "insert into ldap_entries (id,dn,oc_map_id,parent,keyval) > values ((select max(id)+1 from ldap_entries),?,?,?,?)" > #upper_func "upper" > #strcast_func "text" > #concat_pattern "?||?" > #has_ldapinfo_dn_ru no > #schemacheck on > > lastmod off > > > # The base of your directory in database #1 > suffix "dc=example,dc=org" > > # rootdn directive for specifying a superuser on the database. This is > needed > # for syncrepl. > rootdn "cn=admin,dc=example,dc=org" > rootpw secret > # Where the database file are physically stored for database #1 > directory "/var/lib/ldap" > > # For the Debian package we use 2MB as default but be sure to update this > # value if you have plenty of RAM > dbconfig set_cachesize 0 2097152 0 > > # Sven Hartge reported that he had to set this value incredibly high > # to get slapd running at all. See http://bugs.debian.org/303057 > # for more information. > > # Number of objects that can be locked at the same time. > dbconfig set_lk_max_objects 1500 > # Number of locks (both requested and granted) > dbconfig set_lk_max_locks 1500 > # Number of lockers > dbconfig set_lk_max_lockers 1500 > > # Indexing options for database #1 > index objectClass eq > cn,sn,ou > # Save the time that the entry gets modified, for database #1 > lastmod on > > # Where to store the replica logs for database #1 > # replogfile /var/lib/ldap/replog > > # The userPassword by default can be changed > # by the entry owning it if they are authenticated. > # Others should not be able to see it, except the > # admin entry below > # These access lines apply to database #1 only > access to attrs=userPassword,shadowLastChange > by dn="cn=admin,dc=example,dc=org" write > by anonymous auth > by self write > by * none > > # Ensure read access to the base for things like > # supportedSASLMechanisms. Without this you may > # have problems with SASL not knowing what > # mechanisms are available and the like. > # Note that this is covered by the 'access to *' > # ACL below too but if you change that as people > # are wont to do you'll still need this if you > # want SASL (and possible other things) to work > # happily. > access to dn.base="" by * read > > # The admin dn has full write access, everyone else > # can read everything. > access to * > by dn="cn=admin,dc=example,dc=org" write > by * none > > # For Netscape Roaming support, each user gets a roaming > # profile for which they have write access to > #access to dn=".*,ou=Roaming,o=morsnet" > # by dn="cn=admin,dc=example,dc=org" write > # by dnattr=owner write > > ####################################################################### > # Specific Directives for database #2, of type 'other' (can be bdb too): > # Database specific directives apply to this databasse until another > # 'database' directive occurs > #database <other> > > # The base of your directory for database #2 > #suffix "dc=debian,dc=org" > -- regards vinodh i blog @ http://vinsvision.wordpress.com

3 8

Loading the refint module globally?
by Andrew Bartlett 17 Mar '08

17 Mar '08

I've been wondering why I couldn't get the wonders of refint and memberOf to play together, and even went to the extent of writing a testsuite to prove that they could work (indeed, they do). However, I eventually found my problem - while memberOf works very nicely as a global overlay, the refint module does not (yet :-). With it loaded per-backend (for now), it seems to work. Any chance someone could knock me up a patch for that, much like was done so well for memberOf? Thanks, Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Red Hat Inc.

3 10

proxycache examples
by Andy Cobaugh 15 Mar '08

15 Mar '08

I'm working in an environment where the server I wish to use for user and group lookups (through nss_ldap on RHEL) limits the number of queries per IP per day to 200. I want to cache as much as I can locally, for as long as I can. This data hardly ever changes, so the longer I can cache, the better. I'm thinking of caching everything for at least a day, if not longer. Does the pcache overlay currently support such long ttl's? Does anyone have any working pcache configs that can be used to cache the kind of searches performed by nss_ldap ? -- Andy Cobaugh

2 1

Changing attribute values on the consumer
by Kyriakos Stefanidis 14 Mar '08

14 Mar '08

Hello all, Is it possible to change the attribute values on the consumer (of the replication scheme) or add new attributes and preserve them during replication? Im using external scripts that refresh the values/attributes regulary but I was wondering if there is another more "elegant" way Best Regards Kyriakos

3 4

ldap + xsd
by Yan Falken 14 Mar '08

14 Mar '08

Hi, I have one (maybe stupid - so sorry for it :) ) question - is it possible to employ somehow xsd schemas with ldap? My problem is that I need here to document all the possible directory configurations and I'm familiar with xsd and newbie in ldap - so I'm just reasoning if it may be possible to use it for documentation and future schema generation in the next phase. Thanks YF

3 2

Solaris 10 Native LDAP Client TLS
by farhan ahmed 14 Mar '08

14 Mar '08

Hello Guys, I am having some issues to configure LDAP Native client with TLS. Please help me to sort out this issueLDAP Server: Linux (OpenLdap), LDAP Client: Solaris 10 (Native Client)When I run following command to test, it works fine, ldapsearch -v -h test -p 636 -Z -P /var/ldap/cert8.db -b "dc=test,dc=com" -s base "objectclass=*"ldapsearch: started Fri Mar 14 18:11:57 2008ldap_init( test, 636 )filter pattern: objectclass=*returning: ALLfilter is: (objectclass=*)version: 1dn: dc=test,dc=comobjectClass: dcObjectobjectClass: organizationo: test.com web sitedc: test1 matches But When I run ldapclient command to initialize ldapclient, it doesn't work, please guide me where I am doing wrongldapclient -v manual -a defaultServerList=10.10.10.10-a defaultSearchBase=dc=test,dc=com -a authenticationMethod=tls:simple -a serviceAuthenticationMethod=pam_ldap:tls:simple -a serviceAuthenticationMethod=keyserv:tls:simple -a serviceAuthenticationMethod=passwd-cmd:tls:simple-a credentialLevel=proxy -a proxyDN=cn=Manager,ou=People,dc=test,dc=com -a proxyPassword=passwdAfter that when I run ldaplist command, I get following in /var/adm/messagesMar 14 18:15:16 subx05-t1 nfs4cbd[1638]: [ID 293258 daemon.warning] libsldap: Status: 91 Mesg: openConnection: failed to initializeTLS security (security library: bad database.)Please help me guys :) I know I am very near to get it workingThanks,Farhan _________________________________________________________________ New music from the Rogue Traders - listen now! http://ninemsn.com.au/share/redir/adTrack.asp?mode=click&clientID=832&refer…

1 0

Exception while modifying for Open LDAP 2.3 via TLS
by Narayana Murthy Pedapudi 13 Mar '08

13 Mar '08

Please note that I have not used TLSVerifyClient property at all.... # moduleload back_shell.la TLSCipherSuite ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM :+LOW:+SSLv2:+SSLv3:+EXP TLSCACertificateFile /usr/local/var/openldap-data/cacert.pem TLSCertificateFile /usr/local/var/openldap-data/servercrt.pem TLSCertificateKeyFile /usr/local/var/openldap-data/serverkey.pem # Client verification not required #TLSVerifyClient never But I get a different error if I use TLSVerifyclient demand # Client verification not required TLSVerifyClient demand Please find below exception for this java.net.SocketException: Software caused connection abort: recv failed at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at com.sun.net.ssl.internal.ssl.InputRecord.readFully( InputRecord.java:293) at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java :331) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord( SSLSocketImpl.java:723) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.waitForClose( SSLSocketImpl.java:1366) at com.sun.net.ssl.internal.ssl.HandshakeOutStream.flush( HandshakeOutStream.java:103) at com.sun.net.ssl.internal.ssl.Handshaker.sendChangeCipherSpec( Handshaker.java:590) at com.sun.net.ssl.internal.ssl.ClientHandshaker.sendChangeCipherAndFinish (ClientHandshak java:698) at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverHelloDone( ClientHandshaker.java:62 at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage( ClientHandshaker.java:160 at com.sun.net.ssl.internal.ssl.Handshaker.processLoop( Handshaker.java:495) at com.sun.net.ssl.internal.ssl.Handshaker.process_record( Handshaker.java:433) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord( SSLSocketImpl.java:818) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake( SSLSocketImpl.java: 0) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake( SSLSocketImpl.java:1057) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake( SSLSocketImpl.java:1041) at com.sun.jndi.ldap.ext.StartTlsResponseImpl.startHandshake( StartTlsResponseImpl.java:34 at com.sun.jndi.ldap.ext.StartTlsResponseImpl.negotiate( StartTlsResponseImpl.java:208) at com.sun.jndi.ldap.ext.StartTlsResponseImpl.negotiate( StartTlsResponseImpl.java:161) at ModifyAttr.main(ModifyAttr.java:38) Thanks in advance.. -- Narayana Murthy http://narayana-leo.blogspot.com/ http://blogs.sun.com/narayana

1 1

OpenLDAP custom binding operation.
by Sérgio Afonso 13 Mar '08

13 Mar '08

Hello all, We are developing an authentication system based on OpenLDAP. We have created a specific schema, with some password fields intended to be used in different kinds of applications. This attributes (password1, password2, ... passwordx) inherit the userPassword attribute. One of our applications use the ldap_bind method to authenticate its users, and we want it to bind against the attribute password1. However the ldap_bind seems to be hardcoded to just check the userPassword attribute. We have tried using the rwm overlay, and even though we could see the password1 translated to userPassword with an ldapsearch we are unable to bind against it. Is there any overlay besides rwm that could be used to fulfill this authentication scenario? Thanks for any help someone might give us. Best regards, Sérgio Afonso

1 0

LDAP Writes are not propagated to mirror nodes.
by K C, Sachin (Sachin) 13 Mar '08

13 Mar '08

Hello All, I am trying to setup Mirror Mode of replication. Using the configuration files listed below for 2 node setup. The database comes up and after every 2 or 3 writes, the data is not pushed onto the other mirror node. This is happening on both the mirror nodes. I am getting the following error: slap_client_connect: URI=ldap://135.254.229.102:389 DN="uid=<UID>,o=csosso_arc" ldap_sasl_bind_s failed (-1) slap_client_connect: URI=ldap://135.254.229.102:389 DN="uid=<UID>,o=csosso" ldap_sasl_bind_s failed (-1) This is happening after 2 or 3 write operations to the database. The slapd.conf on node 1 is: ================================= database bdb suffix "o=CSOSSO" directory /opt/cso/ldap/db rootdn "uid=<UID>,o=CSOSSO" rootpw <PWD> # cleartext passwords, especially for the rootdn, should # be avoid. See slapd.conf(5) for details. cachesize 10000 index cn pres,eq,sub index sn pres,eq,sub index givenName pres,eq,sub index uid eq index objectclass,entryCSN,entryUUID eq include /opt/cso/ldap/replica/135.254.229.102-390 database bdb suffix "o=CSOSSO_ARC" directory /opt/cso/ldap/db_arc rootdn "uid=<UID>,o=CSOSSO_ARC" rootpw <PWD> # cleartext passwords, especially for the rootdn, should # be avoid. See slapd.conf(5) for details. cachesize 10000 index cn pres,eq,sub index sn pres,eq,sub index givenName pres,eq,sub index uid eq index objectclass,entryCSN,entryUUID eq include /opt/cso/ldap/replica/135.254.229.102-390-arc ========================================= The syncrepl configuration on node 1 is: ========================================= syncrepl rid=1 provider=ldap://135.254.229.102:389 type=refreshAndPersist interval=00:00:01:00 retry="30 +" searchbase="ou=people,o=csosso" filter="(objectclass=*)" scope=sub attrs="*,+" sizelimit="unlimited" timelimit="unlimited" schemachecking=off bindmethod=simple binddn="uid=<UID>,o=CSOSSO" credentials=<PWD> mirrormode on overlay syncprov syncprov-checkpoint 100 1 syncprov-sessionlog 100 ======================================= Same configuration files are used on node 2 except the port numbers and the serverID. Thanks Sachin

5 28

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openldap-technical