Le 11/09/14 12:48, Sebastian Oerding a écrit : > Hello, > > my types are as follows: > > dn: m-oid=2.5.29.14, ou=attributetypes, cn=others, ou=schema > objectclass: metaAttributeType > objectclass: metaTop > objectclass: top > m-oid: 2.5.29.14 > m-name: SubjectKeyIdentifier > m-description: Unique key (except for hash collisions) for X.509 > certificates ac > cording to RFC 5280. > m-equality: caseIgnoreMatch > m-ordering: caseIgnoreMatch > m-syntax: 1.3.6.1.4.1.1466.115.121.1.15 > m-singleValue: TRUE > > dn: m-oid=1.3.6.1.2.1.2.2.1.8, ou=attributetypes, cn=others, ou=schema > objectclass: metaAttributeType > objectclass: metaTop > objectclass: top > m-oid: 1.3.6.1.2.1.2.2.1.8 > m-name: revocation > m-description: Indicates whether a certificate is revoked > m-equality: booleanMatch > m-ordering: booleanMatch > m-syntax: 1.3.6.1.4.1.1466.115.121.1.7 > m-singleValue: TRUE > > dn: m-oid=1.3.6.1.5.5.7, ou=objectclasses, cn=others, ou=schema > objectclass: metaObjectClass > objectclass: metaTop > objectclass: top > m-oid: 1.3.6.1.5.5.7 > m-name: smpki > m-description: X.509 certificates as required due ... > m-must: revocation > m-must: SubjectKeyIdentifier > m-must: userCertificate > > Importing the types works as expected. But any attempt to add an entry > for this object fails. Hence I'm reasoning about the correct way to > add an object class such that I can use it in the tree (I want to have > a node under which I can entries according to my object class). I see nothing wrong with those AT and OC, except that your objectClass has to be declared as STRUCTURAL. Add the two following lines in your ObjectClass definition :
m-typeobjectclass: STRUCTURAL m-supobjectclass: top (the second line is not mandatory, it's just for clarity). Now, when you inject those schema element sin the server, you have to restart it so that they are loaded into the schemaManager, which is in charge of all the checks.
