JDK-6979700 : tighten the attribute sytax check for JNDI/LDAPFrom the reporter
  • Type: Bug
  • Component: core-libs
  • Sub-Component: javax.naming
  • Affected Version: 6u21,7
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2010-08-25
  • Updated: 2010-10-16
  • Resolved: 2010-09-09
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6 JDK 7
6-poolResolved 7Resolved
Related Reports
Duplicate :  
JDK-6979376 - to have ldap filters tolerate underscore character in object identifier
Relates :  
JDK-6916202 - More cases of invalid ldap filters accepted and processed
Description
From the reporter:
--------------------------------------------------------------
..., when I am creating a new entry through JNDI it is allowing me to add an attribute of this type of format. If the object identifier is invalid, then the add request also should fail right? Currently the behavior is that only the search request is failing but add request is succeeding.

Ex:
            // Add the initial required attributes
            Attribute attr3 = new BasicAttribute("description;a_b");
            attr3.add("test_1");
            attrs.put(attr3);
            ctx.createSubcontext("cn=test_1,dc=us,dc=oracle,dc=com",attrs);

But again enforcing this now will impact the apps and it will be a regression for us.
--------------------------------------------------------------

We need to tighten the checking for add/change attribute. please PAY ATTENTION TO the compatibility problem.