In the default schema, several cn=config attributes appear to be missing attributeTypes and are also not defined in the cn=config objectClass (nsslapdConfig).
This causes problems when trying to add ACIs to these attributes, as the directory server doesn't appear to know about them and therefore produces an error like this when trying to add the ACI:
ldap_modify: Invalid syntax (21) additional info: targetattr "nsslapd-localhost" does not exist in schema. Please add attributeTypes "nsslapd-localhost" to schema if necessary. [...]
The fix I'm using is to simply add an attributeType definition for each required attribute to 01core389.ldif, and also update the objectClasses entry for nsslapdConfig, e.g. for nsslapd-localhost:
attributeTypes: ( nsslapd-localhost-oid NAME 'nsslapd-localhost' DESC 'custom defined attribute type' SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 X-ORIGIN 'custom' ) objectClasses: ( 2.16.840.1.113730.3.2.39 NAME 'nsslapdConfig' DESC 'Netscape defined objectclass' SUP top MAY ( cn $ nsslapd-localhost) X-ORIGIN 'Netscape Directory Server' )
This was mostly implemented in 1.3.3 (except for updating the objectclass nsslapdConfig) via ticket https://fedorahosted.org/389/ticket/47437
Per triage meeting...
Metadata Update from @mreynolds: - Issue set to the milestone: 1.3.6 backlog
Metadata Update from @firstyear: - Custom field reviewstatus adjusted to new - Issue close_status updated to: None - Issue tagged with: Complex, Investigate
Metadata Update from @mreynolds: - Custom field reviewstatus reset (from new) - Issue set to the milestone: 1.3.7 backlog (was: 1.3.6 backlog)
Metadata Update from @mreynolds: - Issue set to the milestone: FUTURE (was: 1.3.7 backlog)
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to None - Issue tagged with: Schema
Closing as a duplicate of https://pagure.io/389-ds-base/issue/49201
Metadata Update from @mreynolds: - Issue close_status updated to: duplicate - 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/1722
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: duplicate)
Login to comment on this ticket.