-
Bug
-
Resolution: Fixed
-
P3
-
None
-
b20
-
generic
-
generic
-
Verified
JDK has a global factory filter used by JNDI runtime implementation (RI) to control the set of object factory classes allowed to instantiate objects from remote object references. This filter's scope is all protocols supported by JNDI RI:
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.
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.
- 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