HTTPS <keystore> only supports trust stores and is confusing #29
Description
Monday May 11, 2015 at 22:05 GMT
Originally opened as https://github.com/twogee/missing-link/issues/29
The HTTPS <keystore> element only supports *trust stores*, not *key stores*.
This is confusing and looks to have been caused by the JSSE storage object used
by KeyManagerFactory and TrustManagerFactory being erroneously called KeyStore
and that faulty abstraction leaking into Missing Link.
We have a HTTPS server that requires both a trust store *and* a key store. We
will submit a patch soon that:
a) Renames the existing <keystore> element as <truststore>, as that is what it
is
b) Introduce a new <keystore> element with the same properties - file and
password, in case keystore and truststore are both used and do not share the
same password
c) Change HttpClient under the hood to pass keystore and/or trust store into
the JSSE SSLContext when establishing a HTTPS connection
Original issue reported on code.google.com by stephens...@googlemail.com on 22 Dec 2011 at 4:58