Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cn=config attributes lack attribute schema definitions #1722

Closed
389-ds-bot opened this issue Sep 13, 2020 · 9 comments
Closed

cn=config attributes lack attribute schema definitions #1722

389-ds-bot opened this issue Sep 13, 2020 · 9 comments
Labels
closed: duplicate Migration flag - Issue complex Fix is complex Investigate Issue needs more investigation schema Schema related issue
Milestone

Comments

@389-ds-bot
Copy link

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/48391

  • Created at 2015-12-22 14:24:31 by xdcf
  • Closed at 2020-04-29 16:59:17 as duplicate
  • Assigned to nobody

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' )
@389-ds-bot 389-ds-bot added closed: duplicate Migration flag - Issue complex Fix is complex schema Schema related issue Investigate Issue needs more investigation labels Sep 13, 2020
@389-ds-bot 389-ds-bot added this to the FUTURE milestone Sep 13, 2020
@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2015-12-22 23:32:16

This was mostly implemented in 1.3.3 (except for updating the objectclass nsslapdConfig) via ticket https://fedorahosted.org/389/ticket/47437

@389-ds-bot
Copy link
Author

Comment from nhosoi (@nhosoi) at 2016-01-15 00:55:56

Per triage meeting...

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2017-02-11 23:10:23

Metadata Update from @mreynolds389:

  • Issue set to the milestone: 1.3.6 backlog

@389-ds-bot
Copy link
Author

Comment from firstyear (@Firstyear) at 2017-04-04 04:57:05

Metadata Update from @Firstyear:

  • Custom field reviewstatus adjusted to new
  • Issue close_status updated to: None
  • Issue tagged with: Complex, Investigate

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2017-05-08 22:07:51

Metadata Update from @mreynolds389:

  • Custom field reviewstatus reset (from new)
  • Issue set to the milestone: 1.3.7 backlog (was: 1.3.6 backlog)

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2017-07-05 18:01:19

Metadata Update from @mreynolds389:

  • Issue set to the milestone: FUTURE (was: 1.3.7 backlog)

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2020-04-01 17:17:28

Metadata Update from @mreynolds389:

  • Custom field reviewstatus adjusted to None
  • Issue tagged with: Schema

@389-ds-bot
Copy link
Author

389-ds-bot commented Sep 13, 2020

Comment from mreynolds (@mreynolds389) at 2020-04-29 16:59:19

Closing as a duplicate of #2260

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2020-04-29 16:59:19

Metadata Update from @mreynolds389:

  • Issue close_status updated to: duplicate
  • Issue status updated to: Closed (was: Open)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed: duplicate Migration flag - Issue complex Fix is complex Investigate Issue needs more investigation schema Schema related issue
Projects
None yet
Development

No branches or pull requests

1 participant