[Date Prev][Date Next] [Chronological] [Thread] [Top]

Bug- Enforcing validation when validator is NULL



Hi
When I am trying to add/edit the value to the attribute "protocol information" which is required in our schema I am getting the error
 
Invalid syntax :protocol information: no validator for syntax 1.3.6.1.4.1.1466.115.121.1.42
  
from the earlier mailing list I have found The problem seems to be lack of validations in the schema_init.c source code for attribure 'Protocol Information' 

this attribute protocolInformation is defined in core.schema
 
 {"( 1.3.6.1.4.1.1466.115.121.1.42 DESC 'Protocol Information' )",
  0, NULL, NULL, NULL},
 
 including values like dnPretty ,UTF8StringValidate..etc in the code instead of NULL values will resolve my problem, but then that require the custom build and I have to do for all the attributes where validation is defined as NULL.

I personally feel that for those attributes where validation are NULL in schema_init.c and other schema files, the openLDAP should not force the validation and give this error message, as all these attributes in which validation are not defined becomes unusable .

In Tivoli/Sun and Microsoft Active directory LDAP validation is not enforced where validation is defined as NULL hence I am not getting these kind of error in Tivoli/Sun and Microsoft Active directory for editing of this attribute .
 
So any idea how to resolve this ? there is any way to modify any of the config file in openldap to disable this validation for protocol information ?
do I have to raise bug request for the same and is this going to be fixed in next openLDAP release. ?
  
Any help and suggestions in this direction is highly appreciated.

 thanks and regards
Prashant