|
From: Dunia G. <DGr...@mi...> - 2004-04-14 09:16:00
|
Hi Peter, thank you for your kind reply. I followed your advice but I still can't make my application work properly. Thanx anyway, Dunia ebx...@li... scritti il 04/07/2004 02:00:32 AM > (Disclaimer: I don't actually do this, because for one reason or > another, I comment out most of the Http class used in Hermes, > including the keystore stuff.) > > I believe Hermes uses its own trust store. Look in msh.properties. > xml at //Property/MSH/SSL and use your own keystore, rather than > modifying the one in JAVA_HOME/lib/security. > > PJDM > -- > Peter Mayne > Technology Consultant > Spherion Technology Solutions > Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602 > T: 61 2 62689727 F: 61 2 62689777 > -----Original Message----- > From: Dunia Grandoni [mailto:DGr...@mi...] > Sent: Tuesday, 6 April 2004 7:45 PM > To: ebx...@li... > Subject: [ebxmlms-develop] Hermes & SSL > > Hi all, > I am new to Hermes MSH, so I apologise in advance for the questions > I'm posting. > I cannot make my Hermes MSH application work with https. > I read the previous post 'about Hermes & SSL' and I tried to make > the changes mentioned > there, but I had no success. > Here's what I have to manage: > There's a Tomcat 4.1.27, SSL enabled, on a Windows 2000 platform > (A); an application that uses > msh is running on it, it is used to send (and receive) invoices to a > twin application that is running > on another server (Tomcat 4.1.27, SSL enabled, on a Linux platform (B)). > What I did is creating (with java keytool) a certificate for each > server and then I imported in <JRE>/lib/security/cacerts > of A the certificate of B and viceversa. > When trying to send an invoice from A to B I get an exception: hk. > hku.cecid.phoenix.message.handler.RequestException: sun.security. > validator.ValidatorException: No trusted certificate found > and no message is sent. > Could someone help me configuring msh right? > Thank you so much > Dunia > The information contained in this email and any attachments to it: > (a) may be confidential and if you are not the intended recipient, > any interference with, > use, disclosure or copying of this material is unauthorised and > prohibited; and > (b) may contain personal information of the recipient and/or the > sender as defined > under the Privacy Act 1988 (Cth). Consent is hereby given by the > recipient(s) to > collect, hold and use such information and any personal information > contained in a > response to this email, for any reasonable purpose in the ordinary course of > Spherion's > business, including forwarding this email internally or disclosing > it to a third party. All > personal information collected by Spherion will be handled in accordance with > Spherion's Privacy Policy. If you have received this email in error, > please notify the > sender and delete it. > (c) you agree not to employ or arrange employment for any > candidate(s) supplied in > this email and any attachments without first entering into a > contractual agreement with > Spherion. You further agree not to divulge any information contained > in this document > to any person(s) or entities without the express permission of Spherion. > > |