-
Bug
-
Resolution: Fixed
-
P3
-
None
-
b20
-
generic
-
generic
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8348757 | 17.0.17-oracle | Weibing Xiao | P3 | Resolved | Fixed | b02 |
JDK-8362486 | 17.0.17 | Goetz Lindenmaier | P3 | Resolved | Fixed | master |
JDK-8348758 | 11.0.29-oracle | Weibing Xiao | P3 | Resolved | Fixed | b02 |
JDK-8348759 | 8u471 | Weibing Xiao | P3 | Resolved | Fixed | b02 |
https://docs.oracle.com/en/java/javase/18/docs/api/java.naming/module-summary.html
Adding filters specific to JNDI/LDAP and JNDI/RMI provider implementations would allow finer-grained control over object factories used to instantiate objects in LDAP and RMI systems.
The default values of these new object filters will only allow object factory classes defined by JDK's RMI and LDAP implementations.
- backported by
-
JDK-8348757 Introduce LDAP and RMI protocol-specific object factory filters to JNDI implementation
-
- Resolved
-
-
JDK-8348758 Introduce LDAP and RMI protocol-specific object factory filters to JNDI implementation
-
- Resolved
-
-
JDK-8348759 Introduce LDAP and RMI protocol-specific object factory filters to JNDI implementation
-
- Resolved
-
-
JDK-8362486 Introduce LDAP and RMI protocol-specific object factory filters to JNDI implementation
-
- Resolved
-
- csr for
-
JDK-8291556 Introduce LDAP and RMI protocol-specific object factory filters to JNDI implementation
-
- Closed
-
- relates to
-
SKARA-1640 Bot failed to update and resolve the JBS issue for commit integrated into jdk repo
-
- Resolved
-
- links to
-
Commit openjdk/jdk/d37ce4cd
-
Commit(master) openjdk/jdk17u-dev/39a6bf21
-
Review openjdk/jdk/10578
-
Review(master) openjdk/jdk17u-dev/3738