title: Android app don't trust SSL certifcate but Chrome do
body: <p>We have an internal CA server.</p>
  
  <p>We have an Android app that should communicate via https with our webserver, and have generated the required certificates. When we connect to the server through our app, it fails with the current stacktrace:</p>
  
  <pre><code> Caused by: java.security.cert.CertificateException: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found.
  </code></pre>
  
  <p>But when we browse the server through Android Chrome it works, and we get a green keylock. We have uploaded the certificate on the android device under settings. So it's listed under User certificates. </p>
  
  <p>My question is: Do I need to do anything codewise? I figured that the app would look at the certificates located on the phone, and use this. The way Chrome seems to do. But some guides tell me that I manually have make a keystore and supply this to the SSLFactory (<a href="https://developer.android.com/training/articles/security-ssl.html#UnknownCa" rel="nofollow noreferrer">Link to guide)</a>. But on other pages it seems that this should work out of the box...</p>
  
  <p>Can anyone point me in the right direction?</p>