Bug 555890 - query of cn=schema no longer returns schema
Summary: query of cn=schema no longer returns schema
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: 389
Classification: Retired
Component: Database - General
Version: 1.2.1
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Noriko Hosoi
QA Contact: Chandrasekar Kannan
URL:
Whiteboard:
Depends On:
Blocks: 544927
TreeView+ depends on / blocked
 
Reported: 2010-01-15 20:32 UTC by Rob Crittenden
Modified: 2015-01-04 23:41 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-01-15 21:15:13 UTC
Embargoed:

Attachments (Terms of Use)

Description Rob Crittenden 2010-01-15 20:32:11 UTC 
Description of problem:

Behavior of querying cn=schema has changed

389-ds-base-1.2.3

$ ldapsearch -LLL -x -b "cn=schema"
dn: cn=schema
objectClass: top
objectClass: ldapSubentry
objectClass: subschema
cn: schema

fedora-ds-base-1.2.0-4.fc11.i586

ldapsearch -LLL -x -b "cn=schema" |more
dn: cn=schema
objectClass: top
objectClass: ldapSubentry
objectClass: subschema
cn: schema
objectClasses: ( 2.5.6.0 NAME 'top' DESC 'Standard LDAP objectclass' ABSTRACT 
 MUST objectClass X-ORIGIN 'RFC 2256' )
objectClasses: ( 2.5.20.1 NAME 'subschema' DESC 'Standard LDAP objectclass' SU
 P top AUXILIARY MAY ( dITStructureRules $ nameForms $ dITContentRules $ objec
 tClasses $ attributeTypes $ matchingRules $ matchingRuleUse ) X-ORIGIN 'RFC 2
 252' )
...

Version-Release number of selected component (if applicable):

389-ds-base-1.2.3-1.fc12.x86_64
Comment 1 Rich Megginson 2010-01-15 21:15:13 UTC 
The attributes you need are operational, and are now required to be specified explicitly on the command line, as with other operational attribtes.  For example, the ldapjdk LDAPSchema class uses this as the attribute list:
"*", "ldapSyntaxes", "matchingRules", "attributeTypes", "objectClasses"
Note You need to log in before you can comment on or make changes to this bug.