[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
openLdap neophyte q's
I'm having a bit of trouble porting a 1.2.9 database to 2.0.6. I seem to be
stuck at a very early stage - attributable, no doubt, to my general
inexperience with LDAP. Just for test purposes, I've put together a
super-simplified db. I have a .conf file that looks like:
include ./schema/core.schema
include ./schema/myschema.schema
pidfile ./slapd.pid
argsfile ./slapd.args
database ldbm
suffix "dc=me, dc=com"
rootdn "cn=root, dc=me, dc=com"
rootpw secret
directory ./mydb
and a schema file that looks like:
attribute id cis
objectclass myUser
requires
id
I'm able to successfully 'slapadd' an ldif that looks like:
dn: dc=me, dc=com
dc: me
o: me
objectclass: organization
objectclass: dcObject
dn: cn=root, dc=me, dc=com
cn: root
sn: root
objectclass: person
But, when I try something that uses my custom attribute 'id', as in:
dn: id=user1, dc=me, dc=com
id: user1
objectclass: myUser
I get a 'could not parse entry' error. This is a rather simplified version
of what seems to be happening when I try and port my 1.2 database. I get
similar problems if I specify an index on the attribute 'id'. I running
under Win2K and I've d/l'd a binary version rather than doing builds myself.
I understand this is version 2.06.
Any help most appreciated. Maybe a text called "LDAP for dummies" for
starters.
Tnks,
Paul Johnstone
moneyline
Paul Johnstone, Ph.D.
Director of Technology
1250 Poydras Street, 11th Floor, New Orleans, LA 70113
<mailto:paul.johnstone@moneyline.com>, <http://pjohnstone.com/>