Fedora directory users - Nov 2005 - make an attribute default to object class?

Ok, I have this weird idea that I want to make a new
attribute an allowed attribute of an existing
objectclass
and all its sub-classes, but without modifying the 
definition of the existing class, only thru extension.

For example, if I define a new attribute called 
"myWhackyAttr", and I want to make it part of an
allowed
attribute of nsRoleDefinition (or
nsSimpleRoleDefinition),
so that the attribute is available to all sub-classes.

To do that, I can change the definition of
nsRoleDefinition
in 00core.ldif, which everyone would say "stop right
there,
you shouldn''t do that". 

The other way is, I can create an aux objectclass with

that attribute, and everytime I create a new role,
I have to make sure that I add that object class to
the
new entry. That''s tedious, and might forget it.

Is there a third way to enforce that?

thanks for any hint.

sz



		
__________________________________ 
Start your day with Yahoo! - Make it your home page! 
http://www.yahoo.com/r/hs

speedy zinc wrote:
> Ok, I have this weird idea that I want to make a new
> attribute an allowed attribute of an existing
> objectclass
> and all its sub-classes, but without modifying the 
> definition of the existing class, only thru extension.

I suggest that you get a good reference book to really get a grasp on 
what you are doing instead of using ad-hoc, trial and error sort of 
design methods.


"LDAP Programming, Management, and Integration" by Clayton Donley

Chapter 2 "Understanding the LDAP Information Model" has all the 
information you need.


BR,
Mike

speedy zinc wrote:
>Ok, I have this weird idea that I want to make a new
>attribute an allowed attribute of an existing
>objectclass
>and all its sub-classes, but without modifying the 
>definition of the existing class, only thru extension.
>
>For example, if I define a new attribute called 
>"myWhackyAttr", and I want to make it part of an
>allowed
>attribute of nsRoleDefinition (or
>nsSimpleRoleDefinition),
>so that the attribute is available to all sub-classes.
>
>To do that, I can change the definition of
>nsRoleDefinition
>in 00core.ldif, which everyone would say "stop right
>there,
>you shouldn''t do that". 
>
>The other way is, I can create an aux objectclass with
>
>that attribute, and everytime I create a new role,
>I have to make sure that I add that object class to
>the
>new entry. That''s tedious, and might forget it.
>
>Is there a third way to enforce that?
>  
>
Create a new structural objectclass called MyRole - it will extend 
nsRoleDefinition and include the myWackyAttr attribute (as a MAY 
preferably, not a MUST).  Then, you''ll have to create MyRole roles, for
which there is also not console support.
>thanks for any hint.
>
>sz
>
>
>
>		
>__________________________________ 
>Start your day with Yahoo! - Make it your home page! 
>http://www.yahoo.com/r/hs
>
>--
>Fedora-directory-users mailing list
>Fedora-directory-users@redhat.com
>https://www.redhat.com/mailman/listinfo/fedora-directory-users
>  
>

--- Richard Megginson <rmeggins@redhat.com> wrote:
> >
> Create a new structural objectclass called MyRole -
> it will extend 
> nsRoleDefinition and include the myWackyAttr
> attribute (as a MAY 
> preferably, not a MUST).  Then, you''ll have to
> create MyRole roles, for 
> which there is also not console support.
> 
Yeah, but we want to use the same nsRoleDefinition
as provided by the server, and can be managed through
the console though :)

chris p.



	
		
__________________________________ 
Yahoo! Mail - PC Magazine Editors'' Choice 2005 
http://mail.yahoo.com