Thank you so much Mike.

Alexander

-----Original Message----- From: openldap-technical-bounces@OpenLDAP.org [mailto:openldap-technical-bounces@OpenLDAP.org] On Behalf Of Buchan Milne Sent: Monday, July 05, 2010 11:00 AM To: openldap-technical@openldap.org Cc: Alexander Erameh Subject: Re: Adding new Object Classes

On Friday, 2 July 2010 17:10:50 Alexander Erameh wrote:

Hi,

When I try to add the attached Object Class,

You mean that you are trying to add the schema definition for the objectclass ...

I get the error messages below:

Ldapmodify: invalid format (line 5) entry: "cn=admin,dc=socotherm-africa,dc=com"

This is clearly the wrong place to add a schema ...

Ldapmodify: invalid format (line 19) entry: " "

Ldapmodify: invalid format (line 29) entry: " "

Ldapmodify: invalid format (line 37) entry: " "

Please look at the attached file and tell me what I am doing wrong.

Here is the full qmail.schema converted to OpenLDAP schema ldif, suitable for an ldapadd ...

http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/openldap-extra- schemas/current/SOURCES/qmail.ldif?revision=535500&view=co

And I have just added authldap.ldif:

http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/openldap-extra- schemas/current/SOURCES/authldap.ldif?revision=549784&view=co

Regards, Buchan

On Monday, 5 July 2010 14:38:10 Alexander Erameh wrote:

When I try to add to mine, I get the message below:

Adding new entry "cn=qmail,cn=schema,cn=config" Ldap_add: Insufficient access (50).

This is the Command I used:

ldapadd -xc -W -D "cn=admin,dc=socotherm-africa,dc=com" -f /etc/ldap/schema/qmail.ldif

You didn't provide your configuration, so the assumption I made was that you were using online configuration, in which case you must bind as a user with write access to cn=config (for example the rootdn of the config database, which defaults to 'cn=config', but could have been setup as something different).

The error message here indicates that the DN you are using does not have write access to the config database.

If you aren't using online configuration, but slapd.conf, then you should just include the original schema file (usually ending in .schema) in your slapd.conf, and restart slapd.

Regards, Buchan