[DIRSERVER-205] unrecognized attributes during normalization should not throw exceptions

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: pre-1.0
• Fix Version/s: pre-1.0
• Component/s: ldap
• Assignee: Unassigned
• Reporter: Alex Karasulu
• Created: 24/Oct/05 15:45
• Updated: 07/Feb/06 14:41
• Resolved: 24/Oct/05 15:51

Description

During the normalization process of a DN sometimes its best to not freak out and blow a stack trace when an attribute is not recognized. In this case a best guess is OK. Let's let the schema handling catch the problem which is at a higher level. For now normalized Dn parsers should just leave the value as is if the attribute is unrecognized.

Why is this ok? Again the task of spotting undefined attributes is not the job of the DnParser. It should perform a best guess normalization if it can using schema info. If this info does not exist the parse should not be prevented. This may change in the future when we separate parsing from normalization.

This means we need to check if a NameComponentNormalizer sees an attribute as defined or not. If not then we bypass normalization for the value. If so we normalize. We need to add an isDefined method to NCN and modify the DnParser to adapt to this situation.

Issue Links

• is related to: DIRSERVER-372 Adding a group with invalid member DN corrupts the server