I am unable to add any entries to my Openldap server. Here is the error message that I'm getting:
ldap_bind: Server is unwilling to perform (53) additional info: operation not supported within naming context
I have no idea what this means.
Here is my configuration file (slapd.conf):
# # 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
# 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/lib/openldap # moduleload back_bdb.la # moduleload back_ldap.la # moduleload back_ldbm.la #moduleload back_passwd.la # moduleload back_shell.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
#######################################################################
database bdb
suffix "dc=rcf,dc=unl, dc=edu"
rootdn "cn=Manager,dc=rcf,dc=unl,dc=edu"
# Cleartext passwords, especially for the rootdn, should # be avoided. See slappasswd(8) and slapd.conf(5) for details. # Use of strong authentication encouraged.
rootpw {CRYPT}neyDfOno9u/rg
# 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
# 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@EXAMPLE.COM
#Access controls
defaultaccess none access to attrs=userPassword by self write by * auth access to * by self write by * read by * auth
Here is the ldap.conf file:
# # LDAP Defaults #
# See ldap.conf(5) for details # This file should be world readable but not world writable.
BASE dc=rcf, dc=unl, dc=edu BINDDN cn=Manager,dc=rcf,dc=unl,dc=edu HOST 10.147.99.4 #URI ldap://ldap.example.com ldap://ldap-master.example.com:666
#SIZELIMIT 12 #TIMELIMIT 15 #DEREF never
And here is an example entry that I'm trying to add;
dn: uid=aswearngin,ou=People,dc=rcf,dc=unl,dc=edu uid: aswearngin cn: Amanda surname: Swearngin title: Undergrad groupName: swanson mailLocalAddress: mandamarie05@hotmail.com telephoneNumber: 555-5555 department: Computer S campus: UNL-City college: Arts & Sciences objectClass: account objectClass: posixAccount objectClass: top objectClass: shadowAccount userPassword: {crypt}$1$bGtPvMog$k25rfZEgKjlvsdNb8r1BX0 shadowLastChange: 14154 shadowMax: 99999 shadowWarning: 7 loginShell: /bin/bash uidNumber: 505 gidNumber: 506 homeDirectory: /home/aswearngin
This is the command that I'm using along with several variations of this:
ldapadd -x -D "cn=Manager, dc=rcf, dc=unl, dc=edu" -W -f mysqlpasswd12.ldif
I hope this is enough information to give you a sense of my situation. I am new to this and I am really confused as to how it works, so it would be awesome if someone could help me with this.
Thanks
Amanda
_________________________________________________________________ Want to do more with Windows Live? Learn “10 hidden secrets” from Jamie. http://windowslive.com/connect/post/jamiethomson.spaces.live.com-Blog-cns!55...
On Mon, 6 Oct 2008, Amanda Swearngin wrote:
I am unable to add any entries to my Openldap server. Here is the error message that I'm getting:
ldap_bind: Server is unwilling to perform (53) additional info: operation not supported within naming context
I have no idea what this means.
I only see that string twice in OpenLDAP code: once in back-relay, and once in bind.c. It doesn't look like you're using back-relay, so I'd wonder if ldapwhoami works?
(How something wouldn't be working for the rootdn is beyond me, but that's another story...)
You might want to start simple by using the Quick Start Guide:
http://www.openldap.org/doc/admin24/quickstart.html
If there really is an issue with binding, it's probably due to the ACL. But again, I can't think of how that would affect your use of the rootdn.
--On Monday, October 06, 2008 3:15 PM -0500 Amanda Swearngin mandamarie05@hotmail.com wrote:
And here is an example entry that I'm trying to add;
dn: uid=aswearngin,ou=People,dc=rcf,dc=unl,dc=edu
Did you create the "ou=people,dc=rcf,dc=unl,dc=edu" entry first?
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
openldap-software@openldap.org