javasslhttpscertificateca

why doesn't java send the client certificate during SSL handshake?

I'm trying to connect to a secure web service.

I was getting a handshake failure even though my keystore and truststore had been set correctly.

After several days of frustration, endless googling, and asking everyone around I found out that the only problem was that Java chose not to send the client certificate to the server during the handshake.

Specifically:

  1. Server requested a client certificate (CN=RootCA) - i.e. "give me a cert that is signed by the root CA"
  2. Java looked into the Keystore and only found my client certificate signed by the "SubCA", which is issued by the "RootCA". It didn't bother to look into the truststore...duh OK I guess
  3. Sadly when I tried to add the "SubCA" certificate to the keystore, that didn't help at all. I checked if the certificates were loaded into the keystore. They do, but the KeyManager ignores all certificates except the client one.
  4. All of the above leads to the fact that Java decides it doesn't have any certificates that satisfy the server's request and sends nothing...ta-da handshake failure :-(

My questions:

  1. Is it possible that I added the "SubCA" certificate to the Keystore in a manner that "broke the certificate chain" or something so that the KeyManager only loads the client certificate and ignores the rest? (Chrome and openssl manage to figure that out so why can't Java? - note that the "SubCA" cert is always presented separately as the trusted authority so Chrome correctly packs it along with the client cert during handshake)
  2. Is this a formal "configuration issue" on the server side? The server is a third party. I would expect the server to request a certificate signed by the "SubCA" authority since that's what they provided us with. I suspect that the fact that this works in Chrome and openssl is because they are "less restrictive" and Java just goes "by the book" and fails.

I did manage to put together a dirty workaround for this, but I'm not very happy about it so I'll be glad if anyone can clarify this one for me.

Solution

  • It's possible that you may have imported the intermediate CA certificate into the keystore without associating it with the entry where you have your client certificate and its private key. You should be able to see this using keytool -v -list -keystore store.jks. If you only get one certificate per alias entry, they're not together.

    You would need to import your certificate and its chain together into the keystore alias that has your private key.

    To find out which keystore alias has the private key, use keytool -list -keystore store.jks (I'm assuming JKS store type here). This will tell you something like this:

    Your keystore contains 1 entry

myalias, Feb 15, 2012, PrivateKeyEntry, 
Certificate fingerprint (MD5): xxxxxxxx

    Here, the alias is myalias. If you use -v in addition to this, you should see Alias Name: myalias.

    If you don't have it separately already, export your client certificate from the keystore:

    keytool -exportcert -rfc -file clientcert.pem -keystore store.jks -alias myalias

    This should give you a PEM file.

    Using a text editor (or cat), prepare file (let's call it bundle.pem) with that client certificate and the intermediate CA certificate (and possibly the root CA certificate itself if you want), so that the client-certificate is at the beginning and its issuer cert is just under.

    This should look like:

    -----BEGIN CERTIFICATE-----
MIICajCCAdOgAwIBAgIBAjANBgkqhkiG9w0BAQUFADA7MQswCQYDVQQGEwJVSzEa
....
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
MIICkjCCAfugAwIBAgIJAKm5bDEMxZd7MA0GCSqGSIb3DQEBBQUAMDsxCzAJBgNV
....
-----END CERTIFICATE-----

    Now, import this bundle back together into the alias where your private key is:

    keytool -importcert -keystore store.jks -alias myalias -file bundle.pem