Here is what you need to do at a high-level.
1) Create a certificate and keystore.
2) Insert your certificate into your keystore.
3) Follow the instructions found to enable SSL for which ever HTTP web
server you are using.
4) Update your WebSphere default_host so that it recognizes hostname:443
URL Connections. i.e. Add the hostname:443 to the list, substituting
hostname for how you are going to be calling this from your client
(localhost, the real name, etc.). Add them all, I did.
5) Test the rpcrouter servlet with a browser.
Once you enable your WebSphere App server to work with SSL, you can look at
some of the Apache SOAP FAQs on how to build a SOAP client that communicates
over SSL.
1) Export your certificate.
2) Import it into your client keystore. (see note below.)
3) Insert lines on code into your SOAP client so it knows that it needs to
encrypt and decrypt the HTTP Messages (see FAQ).
4) Run you code.
Note -- I found that once I exported the certificate from my keystore that I
had to change the format of it before I could use it in my client
environment. The way that I did this was to insert it into a browser and
then export it in the correct format.
Good Luck and I wish that I could have been more detailed, but it was a
while ago when I did this.
Craig
-----Original Message-----
From: Irfan Mohammed [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 20, 2001 3:13 PM
To: '[EMAIL PROTECTED]'
Subject: SOAP and SSL and WebSphere
Has anyone installed ssl support for soap in was3.5.4. Any pointers to the
same would be appreciated.
Thanks
Irfan
