Bug 555890

Summary:	query of cn=schema no longer returns schema
Product:	[Retired] 389	Reporter:	Rob Crittenden <rcritten>
Component:	Database - General	Assignee:	Noriko Hosoi <nhosoi>
Status:	CLOSED NOTABUG	QA Contact:	Chandrasekar Kannan <ckannan>
Severity:	medium	Docs Contact:
Priority:	low
Version:	1.2.1	CC:	benl, jgalipea, rmeggins
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-01-15 21:15:13 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	544927

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"