Just following up my own item...
I had the server admins install Sun's version of java and now the tests
run fine. So it had to be something with IBM's JSSE implementation
since the jre is the only thing that changed.
Trent
Trent Ohannessian wrote:
Hello,
Has anyone tried using the IBMJSSEProvider instead of the default Sun
provider when making ssl connections?
I created a pretty simple test locally on my Windows machine to test a
secure site. Works wonderfully.
I put the test on our Linux box (where we want the tests to ultimately
run) and I keep getting a SocketException saying the socket is closed
when trying to make the https connection. If I remove the https and try
to connect via http, it will work for a couple of pages until we require
https at which point it fails with the same SocketException.
After turning on debugging for pretty much everything I noticed the
provider was different between my local and the Linux server so I
started chasing that a little bit. Locally it's set to use Sun's and on
the server it's using IBM's.
I tried setting the connectioninitializer:
<property name="webtest.connectioninitializer"
value="com.canoo.webtest.security.SunJsseClientAuthConnectionInitializer"
/>
....and all that got me was a "Provider not found exception."
I'm trying to not have Sun's implementation installed on the server, so,
here I am. :) Can the IBMJsse be used? Is this even the right wild
goose to be hunting?
Thanks!
Trent
_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest