Subject: Is 'extensibleObject' an auxiliary objectclass?
Author: eLDAP
In response to: What does it look like in schma?
Posted on: 04/27/2010 09:35:32 PM
Yes, here is the definition:
objectClasses: (
1.3.6.1.4.1.1466.101.120.111
NAME 'extensibleObject'
DESC 'LDAPv3 extensible object'
SUP top
AUXILIARY
X-ORIGIN 'RFC 2252'
)
As you can see, '
extensibleObject' does not specify any attributes (MUST or MAY) inside its body. This is a very special objectclass which allow for any attributes being legally resides inside its body. In other words, '
extensibleObject' is a super auxiliary objectclass which can legalize any user defined attributes.
For example:
dn: uid=Babs_Jensen,ou=people,dc=mydomain,dc=com
uid: Babs_Jensen
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: inetOrgperson
objectClass: extensibleObject
cn: Babs Jensen
sn: Jensen
givenname: Barbara
mail: bjensen@example.com
ssn: 333-22-4444
Here, the user defined attribute '
ssn' conforms with schema due to the presence of '
extensibleObject' and thereafter can pass the schema checking.
>
> On 04/27/2010 09:23:24 PM
eLDAP wrote:
objectClasses: (
2.5.6.15
NAME 'strongAuthenticationUser'
DESC 'Standard LDAP objectclass'
SUP top
AUXILIARY
MUST ( userCertificate )
X-ORIGIN 'RFC 2256'
)
References:
