Francois,

Thanks for your quick and helpful reply, I tried what you explained,

 

So I create a new file called 70kevin.ldif and put this into it

 

dn: cn=schema
objectClass: top
objectClass: inetorgPerson
objectClass: subschema
attributeTypes: ( 1.3.6.1.4.1.5923.1.1.1.2 NAME 'policyNos' DESC 'Policy Num
 bers for Insured' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.
 1.15 X-ORIGIN 'user defined' )
objectClasses: ( 1.3.6.1.4.1.12274.1.1.2.1 NAME 'externalUser' DESC '' SUP inet
 orgPerson AUXILLARY MAY ( policyNos ) X-ORIGIN 'user defined' )

I restarted slapd and I got this warning

 

"Entry "cn=schema" missing attribute "sn" required by object class "inetOrgPerson""

 

I can see 'externalUser' but when I try to create a new user, it asks me for the policyNos attribute but not the other attributes of inetOrgPerson, when I try to create the object I get an object violation error.

 

I didnt quite understand this part you mentioned , what else could I be missing.

 

<quote>.....and have your users implement both inetOrgPerson and your auxiliary class. </quote>

----- Original Message ----
From: François Beretti <francois.beretti@gmail.com>
To: kevin james <kevinjj33@yahoo.com>; General discussion list for the Fedora Directory server project. <fedora-directory-users@redhat.com>
Sent: Monday, September 25, 2006 3:59:11 PM
Subject: Re: [Fedora-directory-users] Re: Extending inetOrgPerson's schema to support custom attributes

Hi,

a few thoughts from someone who is not a fedoraDS expert :
- you created a new attribute type, but did not add it to the inetorgperson class definition. So the class itself is not modified. The way the LDIF files are named does not imply you modify a given class. Only the number has a meaning, and this represents the order of the files analysing at the server startup
- I am not sure, but I believe that 99users.ldif should not be modified, because it represents a view of the directory schema, and is not a configuration file. Again, I am really not sure, I don't have a fedora instance at home and can't check this
- standard classes should not be modified. You should create an auxiliary objectClass containing you custom attribute types, and have your users implement both inetOrgPerson and your auxiliary class. This can also be a way to determine if a given user is configured for our application or not (if it implements your aux class or not) To achieve this, you should create a file named, for example, 70kevin.ldif and put all your custom schema in it. Then start your server.


Regards,

François