RE: HTTPS with WebSphere

"Lee, Herman" <[email protected]>
Newsgroups gmane.comp.web.httpunit.devel
Message-ID <C7823B8E4F2E284BADFA7EE2E3B043F1011FAC19@CBSCC-X3-MBVS03.ad.cibc.com>
I figured out how to make https work with WebSphere's jdk, simply:
- change  the variable variable SunJSSE_PROVIDER_CLASS in com.meterware.httpunit.HttpsProtocolSupport from the value "com.sun.net.ssl.internal.ssl.Provider" to "com.ibm.jsse.IBMJSSEProvider"

- and change the variable SSL_PROTOCOL_HANDLER in the same class from the value "com.sun.net.ssl.internal.www.protocol" to "com.ibm.net.ssl.www.protocol"

both ibm packages are inside ibmjsseprovider.jar that comes with WebSphere

>  -----Original Message-----
> From: 	Lee, Herman  
> Sent:	Wednesday, March 29, 2006 3:53 PM
> To:	'[email protected]'
> Subject:	HTTPS with WebSphere
> 
> I am bumping the thread below as no one ever answered Marco's thread.
> I am also interested in knowing whether it is possible to use a different JSSE implementation other than Sun's, for example, IBM's?
> If so, how do I override the default hostname verifier?
> com.sun.net.ssl.HttpsURLConnection.setDefaultHostnameVerifier(String, String) is NOT the right method as WebSphere's implementation doesn't have the com.sun.net.ssl package.
> thanks.
> 
> Herman
> 
> 
> 
> -----Original Message-----
>  	From: Marco Fabbri [mailto:mfabbri@ra...] 
>  	Sent: Wednesday, October 13, 2004 6:04 AM
>  	To: httpunit-develop@li...
>  	Subject: [Httpunit-develop] HTTPS issue
>  	
>  	
>  	Hi all,
>  	I"m trying to use the IBM implementation of JSSE in a httpunit
>  test but I have always the same error:
>  	 
>  	"java.lang.RuntimeException: https support requires the Java
>  Secure Sockets Extension" 
>  	 
>  	even after the static registration of the security.provider.
>  	 
>  	Do someone had used a different JSSE implementation than Sun?
>  	 
>  	Thanks in advance
>  	 
>  	Marco Fabbri
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.