Hi,

I have a custom keystore (abc.jks - with abc.com private key and certificate) which is being used by a specific application for connecting to an external environment.

I would like to know how to configure this abc.jks keystore in my websphere environment for a specific application or application server without disturbing the existing key.p12 used by Websphere.

Could anyone help me on this on priority.

Regards

Hi,

I didn't make this before but i believe that this URL may help:

pic.dhe.ibm.com/infocenter/wasinfo/v7r0/...

//Ahmed

hi ahmed,
Thanks.
i checked that URL before als, but its so complex that i dint wanted to take risk.
for example : it has been given like
'Click a protection_token link in the Protection tokens table.'
but in my was, i have many protection tokens. i dont know which one to select among them and what will be the other impacts by changing this.

regards
ashraf

Hi Ashraf,

  Maybe this is more easy to use.
 
  Dynamic outbound selection of Secure Sockets Layer configurations
  pic.dhe.ibm.com/infocenter/wasinfo/v7r0/...

   "WebSphere® Application Server provides dynamic outbound selection that enables you to choose a specific Secure Sockets Layer (SSL) configuration and certificate alias for each outbound protocol, target host, target port, or any combination of these attributes. You can specify the dynamic selection information for outbound connections from a pure client or from a server that is acting as a client."

   You can create new SSL configuration with your abc.jks
   
   And the select outbound protocol specifying your target host and port and your newly create SSL configuration and the alias of the certificate
  
  For more information and steps to do look in this redbook:
   
     WebSphere Application Server V7.0 Security Guide
      www.redbooks.ibm.com/abstracts/sg247660....
      5.2.3 Securing Web inbound and outbound communication


   Hope this helps.
 
 regards,

Dear All,

Thanks all

Thanks gabriel..  we have fixed the issue by changing the code..

By default - truststore is taking keystore value, if we are not defining truststore explicitly. i.e. keystore=abc.jks=truststore

as a result the truststore  value gets overwritten to abc.jks instead of trust.p12

Hence we fixed the issue by defining both keystore as well truststore explicitly in the code.
keystore=abc.jks
truststore=trust.p12

regards