[Date Prev][Date Next] [Chronological] [Thread] [Top]

value of naming attribute not present in entry



Hi,
 
I am trying to migrate my LDAP Data from an older windows Version of OpenLDAP to the OpenLDAP integrated with Suse Linux 9.0.
 
I have added the new schemata, modified the slapd.conf  and restarted the server.
But Iget the error:
LDAP error 64 : value of naming attribute  id not present in entry
 
Any idea?
 
Here is my ldif:
dn: id=abh,ou=Benutzer,ou=Berechtigungsverwaltung,o=dzbw,c=de
objectClass: benutzer
objectClass: inetOrgPerson
objectClass: organizationalPerson
objectClass: person
objectClass: top
id: abh
cn: Anis
gesperrt: FALSE
passwortDatum: 20040419112940Z
sn: Ben Hamidene
userPassword: e3NzaGF9aX5654MndNSUVmeFgyTjUrUhjRQUnM1ckRZL1BTMzQ3Y1U=
 
Here is my schema:
attributetype (   1.3.6.1.4.1.18677.1.2.1.1.8
 NAME 'id'
 DESC 'ID'
 SYNTAX 1.3.6.1.4.1.1466.115.121.1.38  )
 
objectclass (  1.3.6.1.4.1.59886.1.2.1.2.1
  NAME 'benutzer'
  DESC 'Benutzer'
  SUP inetOrgPerson
  MAY ( gesperrt $ passwortDatum )
  MUST id
 )
 
and my slapd.conf:
 
 
# $OpenLDAP: pkg/ldap/servers/slapd/slapd.conf,v 1.23.2.8 2003/05/24 23:19:14 kurt Exp $
#
# 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/bere_attribute.schema
include  /etc/openldap/schema/cosine.schema
include  /etc/openldap/schema/inetorgperson.schema
include  /etc/openldap/schema/bere_schemata.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  /var/run/slapd/slapd.pid
argsfile /var/run/slapd/slapd.args
 
# Load dynamic backend modules:
# modulepath /usr/lib/openldap/modules
# moduleload back_bdb.la
# moduleload back_ldap.la
# moduleload back_ldbm.la
# moduleload back_passwd.la
# moduleload back_shell.la
 
# 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 is:
# Allow read by all
#
# rootdn can always write!
#User-Mapping
sasl-regexp
          uid=(.*),cn=.*,cn=auth
          id=$1,ou=Benutzer,ou=Berechtigungsverwaltung,o=dzbw,c=de
#Allow everything first
 
access to *
    by * write
 
access to dn.subtree="ou=Berechtigungsverwaltung,o=dzbw,c=de"
    by users write
 
#######################################################################
# ldbm database definitions
#######################################################################
 
database ldbm
suffix  "ou=Berechtigungsverwaltung,o=dzbw,c=de"
rootdn  "id=Admin,cn=Benutzer,ou=Berechtigungsverwaltung,o=dzbw,c=de"
# Cleartext passwords, especially for the rootdn, should
# be avoid.  See slappasswd(8) and slapd.conf(5) for details.
# Use of strong authentication encouraged.
rootpw  secret
# 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
index objectClass eq