| 1 | https://blogs.oracle.com/java-platform-group/entry/diagnosing_tls_ssl_and_https |
| 2 | |
| 3 | |
| 4 | |
| 5 | When making an HTTPS connection, let’s assume that the client threw the following exception due to a failed handshake with the server: |
| 6 | |
| 7 | javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure |
| 8 | |
| 9 | Applying the -Djavax.net.debug=all property from above, the failure associated with this SSLHandshakeException would appear immediately after algorithm negotiation in the logs. |
| 10 | |
| 11 | |
| 12 | Avoid exception: |
| 13 | |
| 14 | VM arguments |
| 15 | |
| 16 | {{{ |
| 17 | -Djavax.net.ssl.trustStore=/home/terryk/.esg/esg-truststore.ts -Djavax.net.ssl.trustStorePassword=changeit |
| 18 | -Djavax.net.debug=all -Dhttps.protocols="TLSv1,SSLv3" |
| 19 | }}} |
| 20 | |
| 21 | |
| 22 | Program arguments it |
| 23 | |
| 24 | {{{ |
| 25 | --oid userOpenIDURL -P password --output outputfil |
| 26 | }}} |