Directory Definition Using LDIF

Perhaps the easiest and most reliable way to define an LDAP directory is through an LDIF script.  It can be independently verified, and, thus, debugged, and then used to build the directory in a single step or incrementally.

Below is an examble LDIF script for building a simple directory suitable for testing wasnd console access and authentication.

---

ldif File

# IBM Directory Server sample LDIF file
#
# The suffix "o=UNC, c=US" should be defined before attempting to load
# this data.

version: 1

dn: o=UNC, c=US
objectclass: top
objectclass: organization
o: UNC

dn: ou=jbsProjects, o=UNC, c=US
ou: jbsProjects
objectclass: organizationalUnit

dn: ou=Users, ou=jbsProjects, o=UNC, c=US
ou: Users
objectclass: organizationalUnit

dn: ou=Groups, ou=jbsProjects, o=UNC, c=US
ou: Groups
objectclass: organizationalUnit

dn: cn=WASND_Admins, ou=Groups, ou=jbsProjects, o=UNC, c=US
objectclass: groupOfNames
cn: WASND_Admins
owner: cn=John Smith, ou=Users, ou=jbsProjects, o=UNC, c=US
member: cn=John Smith, ou=Users, ou=jbsProjects, o=UNC, c=US
member: cn=Alex Boone, ou=Users, ou=jbsProjects, o=UNC, c=US

dn: cn=John Smith, ou=Users, ou=jbsProjects, o=UNC, c=US
objectclass: person
objectclass: organizationalPerson
objectclass: inetOrgPerson
cn: John Smith
sn: Smith
uid: jbs
userPassword: jbs

dn: cn=Alex Boone, ou=Users, ou=jbsProjects, o=UNC, c=US
objectclass: person
objectclass: organizationalPerson
objectclass: inetOrgPerson
cn: Alex Boone
sn: Boone
uid: aboone
userPassword: aboone