[ mx4j-Bugs-1123218 ] Add easier SSL protocol for JMXConnectorServers
"SourceForge.net" <[email protected]>
| Newsgroups | gmane.comp.java.mx4j.devel |
|---|---|
| Message-ID | <[email protected]> |
Bugs item #1123218, was opened at 2005-02-15 16:36 Message generated for change (Comment added) made by simonebordet You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=450647&aid=1123218&group_id=47745 Category: MX4J Tools Group: Release 2.1.1 >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Simone Bordet (simonebordet) Assigned to: Simone Bordet (simonebordet) Summary: Add easier SSL protocol for JMXConnectorServers Initial Comment: Currently the configuration of MX4J's connector servers that use HTTP as application transport protocol to run over HTTPS is to be done externally. Support for soap+ssl, hessian+ssl and burlap+ssl protocols should be added ---------------------------------------------------------------------- >Comment By: Simone Bordet (simonebordet) Date: 2005-02-21 18:29 Message: Logged In: YES user_id=1170988 Implemented. Requires a bit of work to configure the keystore and the web container, but not too much. ---------------------------------------------------------------------- Comment By: Simone Bordet (simonebordet) Date: 2005-02-15 21:08 Message: Logged In: YES user_id=1170988 superbonbon, I am definitely interested in your work. Can we move the discussion to mx4j-dev ? Are you subscribed ? ---------------------------------------------------------------------- Comment By: superbonbon (superbonbon) Date: 2005-02-15 16:55 Message: Logged In: YES user_id=641892 I ve done such patch 2 week ago on the lib to add ssl support with axis and hessian/burlap adapters. However it still needs an external https custom config of the servlet container (jetty used for my tests) to work correctly. I've also encountered some certificate related issues with axis during web service deployment. Axis client tries to connect to the server but the client ssl factory does not accept the server certificate when self signed and crashes. The solution was to configure the axis client to use a fake ssl socket trust manager. Let me know if you want me to integrate my work, cvs acces would be greatly appreciated to do the job. Regards. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=450647&aid=1123218&group_id=47745 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click