|
Bug ID:
|
5107423
|
|
Votes
|
0
|
|
Synopsis
|
Add support for Secure RMI
|
|
Category
|
jndi:rmi
|
|
Reported Against
|
tiger-rc
|
|
Release Fixed
|
mustang(b45)
|
|
State
|
10-Fix Delivered,
request for enhancement
|
|
Priority:
|
4-Low
|
|
Related Bugs
|
6676075
|
|
Submit Date
|
27-SEP-2004
|
|
Description
|
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
factories.
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.
xxxxx@xxxxx 2004-09-28
An enviornment property "com.sun.jndi.rmi.factory.socket" has been provided.
xxxxx@xxxxx 2005-06-27 07:57:53 GMT
Posted Date : 2005-06-27 07:57:53.0
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
