[
http://jira.jboss.com/jira/browse/JBREM-646?page=comments#action_12348716 ]
Claudia Richter commented on JBREM-646:
---------------------------------------
I added a test cenario I implementetd on this issue. Actually I developed on the problem
for my own and found a solution by extracting and using the inner ClientAuthSocketFactory
Class of the org.jboss.test.remoting.transport.socket.ssl.serversocketrefresh Package that
was implemented in the TestServer. I also wrote an extended TransporterServer that is able
to reload itself. But still this might only be a solution for the server side. On the
client side I have no clue, how to solve the problem.
dynamic loading of new keystores during runtime is not possible when
using Transporters (beaming POJOs)
-------------------------------------------------------------------------------------------------------
Key: JBREM-646
URL:
http://jira.jboss.com/jira/browse/JBREM-646
Project: JBoss Remoting
Issue Type: Patch
Security Level: Public(Everyone can see)
Components: transporter
Environment: ??
Reporter: Claudia Richter
Assigned To: Tom Elrod
Attachments: TruststoreBug.zip
when running a Transporter Server and a Transporter Client, using SSL connection, the
Transporter Server does not recognise changes within its Truststore, if this is updated.
Means, if the Client is not trusted when starting the Server, it will not be trusted for
future request until the Server is restarted. It would be better to have a Server that is
able to recognise Truststore changes. This feature is already implemented for other
transports (no Transporters) as described in issue
http://jira.jboss.com/jira/browse/JBREM-427.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira