The objectClass (which is an attribute in and of itself) defines what "must" or "could" be used in an entry. Choose the collection of objectClass attribute for each type of data needed, for example:

dn: cn=bakshi,ou=people,dc=example,dc=com objectClass: top objectClass: inetOrgPerson cn: bakshi sn: bakshi userPassword: a_password description: a user entry

On Jun 8, 2009, at 3:10 AM, J. Bakshi wrote:

Dear all,

greetings to all. Hope I have joined the right list to discuss about openldap technology.

I am working with typo3 and openldap. Typo3 is a CMS ( content management system ) just like Drupal, Joomla etc.. I like to implement an openldap based system where I can have a organization based structure like department, company etc and can store persons with their name, address, contact along with userid/password which will be used to authenticate the front end user login in typo3.

To start with I need a well designed ldif file. I have already get some example ldif from internet but those are missing the useris/password authentication. More over the " objectclass: organizationalPerson " " objectclass: inetOrgPerson " "objectClass: dcObject" "objectClass: organization" are very much confusing :-(

Could any one kindly enlighten me a little about those "objectcalss" and which one is best suited for my requirement ? A sample ldif file with little explanation will help me a great.

Thanks

"top" is the ancestor of all objectClasses. I do not know why your utility does not work. If it were me, I would test your LDAP setup by using ldapsearch to verify that the entries can be returned before using some other layer:

ldapsearch -h hostname -p port -s base -b 'uid=scarter,ou=people,dc=ceu,dc=hu' '(objectClass=*)' dn

On Jun 8, 2009, at 8:19 AM, J. Bakshi wrote:

Terry Gardner wrote:

...

The objectClass (which is an attribute in and of itself) defines what "must" or "could" be used in an entry. Choose the collection of objectClass attribute for each type of data needed, for example:

dn: cn=bakshi,ou=people,dc=example,dc=com objectClass: top objectClass: inetOrgPerson cn: bakshi sn: bakshi userPassword: a_password description: a user entry

Thanks a lot for your response. It seems that we can use more than one object class. Though interested to know the objectclass:top. Shall I need to do any modification to slapd.conf ( beside base DN and Administrative user/Password ) to work with ldap ? I have followed this sample ldif ( from net ) but phpldapadmin does not show me the entries

dn: dc=ceu,dc=hu
objectclass: dcObject
objectclass: organization
o: CEENET Workshop 2001

dn: ou=people,dc=ceu,dc=hu
objectclass: organizationalUnit
ou: people

dn: uid=scarter,ou=people,dc=ceu,dc=hu
cn: Sam Carter
sn: Carter
givenname: Sam
objectclass: top
objectclass: person
objectclass: organizationalPerson
objectclass: inetOrgPerson
ou: Accounting
ou: People
l: Sunnyvale
uid: scarter
mail: scarter@tutorial.hu
telephonenumber: +1 408 555 4798
facsimiletelephonenumber: +1 408 555 9751
roomnumber: 4612
userpassword: sprain

...

On Jun 8, 2009, at 3:10 AM, J. Bakshi wrote:

...

Dear all,

greetings to all. Hope I have joined the right list to discuss about openldap technology.

I am working with typo3 and openldap. Typo3 is a CMS ( content management system ) just like Drupal, Joomla etc.. I like to implement an openldap based system where I can have a organization based structure like department, company etc and can store persons with their name, address, contact along with userid/ password which will be used to authenticate the front end user login in typo3.

To start with I need a well designed ldif file. I have already get some example ldif from internet but those are missing the useris/ password authentication. More over the " objectclass: organizationalPerson " " objectclass: inetOrgPerson " "objectClass: dcObject" "objectClass: organization" are very much confusing :-(

Could any one kindly enlighten me a little about those "objectcalss" and which one is best suited for my requirement ? A sample ldif file with little explanation will help me a great.

Thanks

Emmanuel Lecharny wrote:

...

dn: dc=ceu,dc=hu objectclass: dcObject objectclass: organization o: CEENET Workshop 2001

You have to add a dc=ceu attribute/value in this entry, as it's a mandatory attributeType for the dcObject ObjectClass (also because it's the first RDN of your DN...)

dn: dc=ceu,dc=hu objectclass: dcObject objectclass: organization o: CEENET Workshop 2001 dc: ceu

check that : http://ldap.akbkhome.com/index.php/objectclass/dcObject.html

Thanks, I'll do it in that way