Websphere (v7) and one way ssl client code

[William Barnes]

Is it "one way ssl", or "1 way ssl"? Not sure what is the most common usage. (Actually I just said that to increase the search result hittage. Yes, I just made up that word.)
I have java code which can act as a client that supports one way ssl. I am using Websphere and am assuming that I am suppose to be using some of it's feature(s) to do this. One possible example is having Websphere handle the ssl certificate. I guess?
Can anyone offer any tips, or links, about how to make use of Websphere features to support a one way ssl client?
Thanks.

[Deepak Pant]

Yes it is called one way SSL. Is your client a Java client ?

Typically the process is as follows:
1. Create a new self-signed certificate. In production replace this step with certificate request and CA issued certificate.
2. Export the Certificate from the WAS Console.
3. Create a new truststore (say clientTrustStore.jks). The store will have a password etc.
4. Import the certificate extracted in Step #2 into clientTrustStore.jks.
5. Now when you establish the HTTPS connection from client application you will set the name of the trust store, password etc.

Step 1 and 2 can be done using WAS console. Step 3 & 4 using command line keystore utility. Step 5 is in your java client code.

Hope this helps

[William Barnes]

Still a little confusing.
What I can do now, using regular Java outside of Websphere. 1] Go to company certificate authority, get public key. 2] Make keystore/truststore with CA public key. 3] Run my code, which successfully supports one way ssl. 4] Works.
I know I can bring my java client into Websphere. What about the keystore?