JDK-5107423 : Add support for Secure RMI
  • Type: Enhancement
  • Component: core-libs
  • Sub-Component: javax.naming
  • Affected Version: 5.0
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: solaris_2.5.1
  • CPU: sparc
  • Submitted: 2004-09-27
  • Updated: 2017-05-16
  • Resolved: 2005-07-22
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
6 b45Fixed
Related Reports
Relates :  
The Sun's JNDI/RMI Registry Service Provider does not allow to perform
operations on an RMI Registry that has been secured with SSL socket

It would be nice to be able to pass the SSL Client Socket Factory in
the hashtable passed in to the InitialContext so that the provider could
call LocateRegistry.getRegistry(host, port, sslClientFactory) later on.

WORK AROUND No workaround available through JNDI. Need to manipulate the rmi registry through the java.rmi.registry APIs.

EVALUATION Doable for mustang. ###@###.### 2004-09-28 An enviornment property "com.sun.jndi.rmi.factory.socket" has been provided. ###@###.### 2005-06-27 07:57:53 GMT