Hi Dimuthu,
Isn't it supposed to be automatically since we have this property in the
rampart config of the policy?
I can say that rampart actually extract those and use them.
I'll try your solution to see if it works.
So, the EPR should be the same but using the ssl port right?
Does anyone has any experience with the transport binding?
thanks,
Nencho
2007/5/16, Dimuthu <[EMAIL PROTECTED]>:
Hi Nencho,
Couple of hours ago I was looking at how to configure ssl in Axis2
client side becuase of Rampart-42. I found this article [1]. Basically
if you have JSSE, set the following four parameters in the client side
properly and things should work smoothly when you give the EPR
correctly.
System.setProperty("javax.net.ssl.keyStorePassword", "password");
System.setProperty("javax.net.ssl.keyStoreType", "JKS");
System.setProperty("javax.net.ssl.trustStore", "client-truststore.jks");
System.setProperty("javax.net.ssl.trustStorePassword", "trustPass");
I haven't tried it. But it should work.
By the way regarding Rampart-42, we can automate the client side SSL
configuration as much as possible in the Rampart when it comes to
TransportBinding assertion, but serverside has to be handled manually.
What do you think? I don't see a better solution.
Cheers,
Dimuthu
[1]http://java.sun.com/products/jsse/INSTALL.html
On Wed, 2007-05-16 at 13:33 +0300, Nencho Lupanov wrote:
> Hi all,
>
> I am testing the TransportBinding assertion with UsernameToken.
> Do I need some furthure configuration on tomcat in order to enable ssl?
> I already configured ssl on port 9443.Is that enough?
>
> Does the enpoint needs to use this port?Do I only have to change the
port at
> the endpoint or something?
>
> Thanks,
> Nencho
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
