From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Description of problem:
When playing with openldap schema conversion to FDS I discover this issue below:
RFC 2252 say for object class:
[ "SUP" oids ]
oids = woid / ( "(" oidlist ")" )
oidlist = woid *( "$" woid )
One of my converted schema contains this line;
SUP (inetOrgPerson $ PureFTPdUser )
And based on RFC 2252 it is RFC compliant.
But FDS complain with error below:
error code 20 (Type or value exists) - object class ispmanDomainUser: Superior object class "(inetOrgPerson" does not exist
SUP inetOrgPerson $ PureFTPdUser
is working without any FDS complains.
So I guess FDS is not RFC compliant on this point.
Yacine (Yada on #fedora-ds)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. use parenthesis in a schema for an object class SUP declaration
2. restart FDS
Actual Results: error code 20 (Type or value exists) - object class "foo": Superior object class "(bar" does not exist
Expected Results: Should restart without errors and take the SUP () declaration into account.
*** Bug 181466 has been marked as a duplicate of this bug. ***
I believe the current parser is space sensitive (and really should not be) - it
requires a space between the bracket and the list item.
Correct it work fine with:
SUP ( inetOrgPerson $ PureFTPdUser )
This falls under the category of "improve schema parsing" and "RFC correctness"
Created attachment 345962 [details]
Our schema parser requires a space after the opening paran
when multiple SUP objectclasses are listed in the definition
of an objectclass. The RFCs show that a space is not required.
This patch simply removes the requirement that a space be
present after the opening paran.
Pushed patch to master.
verified RHEL 4
Successfully added the following schema without spaces between the brackets
objectclasses: (1.22.333.4444 NAME 'myMozOC' DESC 'Objectclass that contains MozillaAttribute' SUP top STRUCTURAL MUST (cn $ MozillaAttribute))