(ITS#4037) syntax error in objectclass definition not caught

[ydirson@altern.org]

Full_Name: Yann Dirson
Version: 2.2.13 (rhel4 2.2.13-2)
OS: rhel 4
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (62.160.59.37)


When an objectclass definition has an extraneous closing paren, causing the
definition to end prematurely, the following statements, which were intended to
be part of the definition, do not cause any error.  Here is a sample one:

objectclass ( 1.1.1 NAME 'projectaccount'
	SUP top STRUCTURAL )
	MUST ( projectgroup ) )

slaptest reports no error here.  If I suppress the extraneous parent before the
MUST clause, then slaptest complains about the projectgroup attribute not being
defined, as expected.

It is an important issue, since one may think to have a strict schema, ensuring
the occurence of certain attributes, whereas openldap will happilly let objects
in, which do not respect the intended schema.  Indeed, I noticed the issue while
I wondered why my knowingly-incomplete objects were accepted by slapadd...