-
Bug
-
Resolution: Fixed
-
P4
-
8, 9
-
b62
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8084812 | emb-9 | Omair Majid | P4 | Resolved | Fixed | team |
JDK-8130985 | 8u65 | Omair Majid | P4 | Resolved | Fixed | b05 |
JDK-8129583 | 8u60 | Omair Majid | P4 | Resolved | Fixed | b22 |
JDK-8138273 | emb-8u65 | Unassigned | P4 | Resolved | Fixed | b05 |
JDK-8130592 | emb-8u60 | Omair Majid | P4 | Resolved | Fixed | b22 |
RFC2255 [1] allows any of attribute, scope, filter and extension to be empty. Code in com.sun.jndi.ldap package expects empty values to be represented by null, but LdapURL parsing method leaves optional parameters as "" (empty string).
Test URL: ldap://localhost:10389/ou=RefPeople,dc=example,dc=com????
Expected result:
ldapUrl.getAttributes() == null
ldapUrl.getFilter() == null
ldapUrl.getScope() == null
ldapUrl.getExtension() == null
Actual result:
ldapUrl.getAttributes() == ""
ldapUrl.getFilter() == ""
ldapUrl.getScope() == ""
ldapUrl.getExtension() == ""
[1] https://tools.ietf.org/html/rfc2255#section-3
Test URL: ldap://localhost:10389/ou=RefPeople,dc=example,dc=com????
Expected result:
ldapUrl.getAttributes() == null
ldapUrl.getFilter() == null
ldapUrl.getScope() == null
ldapUrl.getExtension() == null
Actual result:
ldapUrl.getAttributes() == ""
ldapUrl.getFilter() == ""
ldapUrl.getScope() == ""
ldapUrl.getExtension() == ""
[1] https://tools.ietf.org/html/rfc2255#section-3
- backported by
-
JDK-8084812 Empty optional parameters of LDAP query are not interpreted as empty
- Resolved
-
JDK-8129583 Empty optional parameters of LDAP query are not interpreted as empty
- Resolved
-
JDK-8130592 Empty optional parameters of LDAP query are not interpreted as empty
- Resolved
-
JDK-8130985 Empty optional parameters of LDAP query are not interpreted as empty
- Resolved
-
JDK-8138273 Empty optional parameters of LDAP query are not interpreted as empty
- Resolved