× 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.


  1.  Home
  2. JAVA400-L
  3. March 2006

java.security - changing to use pure java JSSE without editing system files?

My problem is that our customer wants to accept payloads sent over https to a small OS/400 machine where resource usage is at premium - so the full WebSphere is not immediately relevant - and where we want a simple solution independant of which machine it actually runs on, and then AFAIK it would be best to use Java KeyStores instead. Then we can prepare everything inhouse and then remote deploy.
I am therefore investigating how to get SSL up and running with a stock Java Web Container, where we currently look at Jetty 5.1.10 but are open to other suggestions, but I have had quite a bit of trouble figuring out how to get it running right.
Apparently the default configuration of JSSE on OS/400 uses the implementation inside OS/400 instead of the pure java I expected, but even so when specifying the IbmX509 algorithm explicitly I cannot make this work.
It appears to me that the usual way to remidy this is to change the java.security file directly on the system in question. I would rather have that I could do some changes in the actual program only, so this would not be a global issue.
But right now, I just want to know if there is anyone who have made HTTPS work under OS/400, and how did you do it? 

Thanks in advance for any help :)

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.