Re: java.security - changing to use pure java JSSE without editing systemfiles? -- JAVA400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Urbanek, Marty wrote:

Thorbj?rn,

This is not the complete answer to your question, but maybe it will help. 
Please take note of the os400.security.properties property, which will allow 
you to point your JVM to a unique java.security file for your program without 
having to modify the default file for the system.

I didn't see this when browsing through the docs, so I'll keep it inmind. Also the remark about using native certificates was good.

I found that my problem appeared to be that the IbmX509 protocol wasmapped to native certificates, and I needed the pure Java provider. Imanaged to get Jetty up and running, by adding a configurable providerfield to SSLListener.java in Jetty and this small modification increateFactory()


      if (_provider == null) {
           context = SSLContext.getInstance(_protocol);
       } else {
           context = SSLContext.getInstance(_protocol, _provider);
       }

I'll submit a patch to Jetty, and investigate if the same is necessarywith Tomcat.


Thanks to those who responded :)
--
 Thorbjørn

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.