|
Urbanek, Marty wrote:
I didn't see this when browsing through the docs, so I'll keep it in mind. Also the remark about using native certificates was good.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 found that my problem appeared to be that the IbmX509 protocol was mapped to native certificates, and I needed the pure Java provider. I managed to get Jetty up and running, by adding a configurable provider field to SSLListener.java in Jetty and this small modification in createFactory()
midrange.com
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 necessary
with Tomcat.
Thanks to those who responded :) -- Thorbjørn
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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 copyright@midrange.com.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
