#47818 It is possible to create object with auxiliary object class only
Closed: wontfix by mreynolds. Opened by pspacek.

I have accidentally created an object which has only auxiliary object class and 389 allowed me to do it.

version: 389-ds-base-1.3.2.16-20140526081843.fc20.x86_64
from http://copr.fedoraproject.org/coprs/lkrispen/132test/

LDIF I used:

dn: ipaPublicKey=test,cn=keys,cn=sec,cn=dns,dc=ipa,dc=example
changetype: add
objectClass: ipaPublicKeyObject
objectClass: top
ipaPublicKey: test

Schema:

attributeTypes: (2.16.840.1.113730.3.8.11.53 NAME 'ipaPublicKey' DESC 'Public key as DER-encoded SubjectPublicKeyInfo (RFC 5280)' EQUALITY octetStringMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.40 X-ORIGIN 'IPA v4' )
objectClasses: (2.16.840.1.113730.3.8.12.24 NAME 'ipaPublicKeyObject' DESC 'Wrapped public keys' SUP top AUXILIARY MAY ( ipaPublicKey ) X-ORIGIN 'IPA v4' )

389 DS doens't differentiate between structural and auxiliary objectclasses, which is why you are able to create an entry with only an auxiliary objectclass. Similarly, you cna create an entry with multiple structural objectclasses. It has always been this way, and changing the behavior would be difficult due to backwards compatibility concerns. It would be nice to be RFC correct in this area, but I don't see this changing any time soon.

Metadata Update from @nkinder:
- Issue set to the milestone: FUTURE

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to None
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/1149

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata