title: `p12` file work in Firefox RestClient but not work in WebSphere
body: <p>I have a java web application that runs in WebSphere that need to call to third party service (IBM) to get some response.</p>
  
  <p>At first IBM give me a <code>p12</code> file, which is contain client certificate, and I test it in Firefox <code>RestClient</code>, the call success and I am getting response code 200 in the <code>RestClient</code>. Else, I will get 403 forbidden. So this is proof that the <code>p12</code> provided by third party is correct. Please correct me if my statement is wrong.</p>
  
  <p>Thus, I happily import this <code>p12</code> file into my CellDefaultKeyStore to test the connection on my application. Unfortunately, after I import this p12 file, the nodes status become "unknown", and I cant even "synchronize" them. And when I check server log, I keep seeing</p>
  
  <pre><code>com.ibm.jsse2.util.j: PKIX path building failed: java.security.cert.CertPathBuilderException: PKIXCertPathBuilderImpl could not build a valid CertPath.; internal cause is: 
      java.security.cert.CertPathValidatorException: The certificate issued by xxx is not trusted; internal cause is: 
      java.security.cert.CertPathValidatorException: Certificate chaining error
  </code></pre>
  
  <p>After that I remove it from <code>CellDefaultKeyStore</code> try to import it into <code>NodeDefaultKeyStore</code>, the node issue gone, the node can sync back and my app can call to the third party successfully. I think this is done of my job today, however, this solution is not stable, its only work some times, not every time. The node status will still become "unknown" after a moment, or, if I run <code>./stopManager.sh</code> and <code>./startManager.sh</code>, the node issue will immediately come back.</p>
  
  <p>I have try run <code>./stopNode.sh</code> and <code>./startNode.sh</code>, there are no error in the log of this 2 shell script. But the WAS Console UI there still showing status is <code>unknown</code>, and I cant even stop start my server through WAS Console.</p>
  
  <p>At first I am thinking its maybe display issue, but this issue will solve if I delete the <code>p12</code> file from my <code>NodeDefaultKeyStore</code>. </p>
  
  <p>I try google around but end up still cant find any clue. I am not sure is it my configuration or the <code>p12</code> file having problem.</p>
  
  <p>Which log should I refer to see why the node status will become <code>unknown</code>, or what else I can continue to debug/troubleshoot on this?</p>