-
Bug
-
Resolution: Duplicate
-
P4
-
6u21, 7
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2201100 | 7 | Xuelei Fan | P3 | Closed | Duplicate |
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.
--------------------------------------------------------------
..., 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.
- backported by
-
JDK-2201100 tighten the attribute sytax check for JNDI/LDAPFrom the reporter
-
- Closed
-
- duplicates
-
JDK-6979376 to have ldap filters tolerate underscore character in object identifier
-
- Resolved
-
- relates to
-
JDK-6916202 More cases of invalid ldap filters accepted and processed
-
- Resolved
-