Tried adding the extensibleObject class as a
"default:schema-compat-entry-attribute" and it just results in an extra error:
[16/Jul/2021:15:06:28.366345301 -0400] - ERR - slapi_entry_schema_check_ext - Entry
"cn=test.lab.local,cn=adcomputers,cn=compat,dc=lab,dc=local" has unknown object
class "computer"
[16/Jul/2021:15:06:28.368032010 -0400] - WARN - str2entry_dupcheck - Duplicate value for
attribute type objectClass detected in entry
cn=test.lab.local,cn=adcomputers,cn=compat,dc=lab,dc=local. Extra value ignored.
I suspect that is because I already had it as a "default:objectClass:
extensibleObject". See the configuration below.
dn: cn=adcomputers, cn=Schema Compatibility, cn=plugins, cn=config
default:objectClass: top
default:objectClass: extensibleObject
default:cn: adcomputers
default:schema-compat-container-group: cn=compat, $SUFFIX
default:schema-compat-container-rdn: cn=adcomputers
default:schema-compat-search-base: cn=computers, cn=accounts, $SUFFIX
default:schema-compat-search-filter: (&(fqdn=*)(objectClass=ipaHost))
default:schema-compat-entry-rdn: cn=%first("%{fqdn}")
default:schema-compat-check-access: yes
default:schema-compat-entry-attribute: objectclass=extensibleObject
default:schema-compat-entry-attribute: objectclass=computer
default:schema-compat-entry-attribute: cn=%{fqdn}
default:schema-compat-entry-attribute: sAMAccountType=805306369
default:schema-compat-entry-attribute: dNSHostName=%{fqdn}
I really want/need to avoid manipulating their actual schema. I really want this all self
contained as a compatibility plugin config that doesn't touch their existing
data/schema. I would tell them just to ignore the unknown objectclass errors, but I would
like it to be cleaner than that.
Any other thoughts?