Populating your DIT.
Our aim is to populate our LDAP Server by the following company structure of organisational units and persons:
The Apache Directory Studio allows for conveniently accessing and modifying your server's LDAP trees.
Tip
You may want to adjust occurrences of
dc=betrayer;dc=com
by your configured DIT root.
-
You need your initial configuration
admin
password to perform a bind operation using thecn=admin,dc=betrayer,dc=com
DN. -
If you choose “Use existing entry as template” don't forget to purge your copy's entryCsn attribute belonging to your template data record being unique within your DIT.
-
Suitable objectClass and unique key attribute choices:
When you are finished an Apache Directory Studio export dump of your tree might look like:
dn: dc=betrayer,dc=com
objectClass: organization
objectClass: dcObject
objectClass: top
dc: betrayer
o: betrayer.com
dn: cn=admin,dc=betrayer,dc=com
objectClass: organizationalRole
objectClass: simpleSecurityObject
cn: admin
userPassword:: e1NTSEF9cEhFK0VQT0cyZ3lSeU9nanZGcXNXT2I1ekdzR2w5Q0Q=
description: LDAP administrator
dn: ou=departments,dc=betrayer,dc=com
objectClass: top
objectClass: organizationalUnit
ou: departments
dn: ou=software,ou=departments,dc=betrayer,dc=com
objectClass: top
objectClass: organizationalUnit
ou: software
dn: ou=financial,ou=departments,dc=betrayer,dc=com
objectClass: top
objectClass: organizationalUnit
ou: financial
dn: ou=devel,ou=software,ou=departments,dc=betrayer,dc=com
objectClass: top
objectClass: organizationalUnit
ou: devel
dn: ou=testing,ou=software,ou=departments,dc=betrayer,dc=com
objectClass: top
objectClass: organizationalUnit
ou: testing
dn: uid=bean,ou=devel,ou=software,ou=departments,dc=betrayer,dc=com
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: inetOrgPerson
cn: Jim Bean
sn: Bean
givenName: Jim
mail: bean@betrayer.com
uid: bean
userPassword:: e3NtZDV9YVhKL2JlVkF2TDRENk9pMFRLcDhjM3ovYTZQZzBXeHA=
dn: uid=smith,ou=financial,ou=software,ou=departments,dc=betrayer,dc=com
...