-
Bug
-
Resolution: Fixed
-
P3
-
6u17-rev
-
None
-
b86
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2188248 | 6u21 | Xuelei Fan | P3 | Resolved | Fixed | b01 |
Ldap filters indentified as invalid by RFC: http://tools.ietf.org/html/rfc4515 are accepted and processd. The JDK ldap code should throw an exception when such invalid filters are encountered, instead of processing and passing the ldap request to the LDAP servers which always throw an exception. Following are examples of invalid filters:
1. "((objectClass=*)&(uid=*))"
2. &(objectClass=*)(uid=*)
3. ((objectCategory=person)(objectClass=user)(!(cn=user1*)))
4. ((&(objectClass=user)(cn=andy*)(cn=steve*)(cn=margaret*)))
1. "((objectClass=*)&(uid=*))"
2. &(objectClass=*)(uid=*)
3. ((objectCategory=person)(objectClass=user)(!(cn=user1*)))
4. ((&(objectClass=user)(cn=andy*)(cn=steve*)(cn=margaret*)))
- backported by
-
JDK-2188248 More cases of invalid ldap filters accepted and processed
-
- Resolved
-
- relates to
-
JDK-6979376 to have ldap filters tolerate underscore character in object identifier
-
- Resolved
-
-
JDK-6972409 Cease emitting LDAP filter debug messages
-
- Closed
-
-
JDK-6449574 Invalid ldap filter is accepted and processed
-
- Closed
-
-
JDK-6979700 tighten the attribute sytax check for JNDI/LDAPFrom the reporter
-
- Closed
-