I ran following command to check whether Shield is able to connect when connected via TLSv1 using openssl:
openssl s_client -connect 127.0.0.1:9300 -tls1
It results in following output:
CONNECTED(00000003)
139722194011808:error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure:s3_pkt.c:1260:SSL alert number 40
139722194011808:error:1409E0E5:SSL routines:SSL3_WRITE_BYTES:ssl handshake failure:s3_pkt.c:596:
no peer certificate available
No client certificate CA names sent
SSL handshake has read 7 bytes and written 0 bytes
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
SSL-Session:
Protocol : TLSv1
Cipher : 0000
Session-ID:
Session-ID-ctx:
Master-Key:
Key-Arg : None
PSK identity: None
PSK identity hint: None
SRP username: None
Start Time: 1446509729
Timeout : 7200 (sec)
Verify return code: 0 (ok)
And before doing that I added the following properties to yml file:
shield.ssl.protocol: TLSv1
shield.ssl.supported_protocols: SSLv2Hello, SSLv3, TLSv1, TLSv1.1, TLSv1.2
Which means there's something definately wrong with configuration/certificate.