[精讚] [會員登入]
1165

更新java版本後一定要做的事情

how to deal with PKIX path building failed issue after upgrade java sdk version in IDE

分享此文連結 //n.sfs.tw/14820

分享連結 更新java版本後一定要做的事情@外行中的外行
(文章歡迎轉載,務必尊重版權註明連結來源)
2020-11-23 21:58:55 最後編修
2020-11-20 23:34:34 By jung
 

每次編譯器更新java sdk版本後,例如這次我從openjdk11.0.5升級到11.0.8

就會出現:javax.net.ssl.SSLHandshakeException: PKIX path building failed

編譯或執行時出錯

找到解法如下:

1.先下載該網站公開憑證

例如我想連到 google.com 透過 HTTPS執行程式或下載

使用openssl先產生該網站的crt憑證檔案

openssl s_client -connect google.com:443 -servername google.com:443 < /dev/null | sed -ne '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p' > public.crt

2.再匯到jvm的cacert 中,這邊一定要找到jdk版本中keytool的絕對路徑

例如:/Library/Java/JavaVirtualMachines/adoptopenjdk-11-openj9.jdk/Contents/Home/bin/keytool

<JAVA_HOME>/bin/keytool -import -alias <server_name> -keystore <JAVA_HOME>/jre/lib/security/cacerts -file public.crt

 

這樣就可以解決了

參考文件

https://confluence.atlassian.com/kb/how-to-import-a-public-ssl-certificate-into-a-jvm-867025849.html

END

你可能感興趣的文章

how to make wicket web application runs under docker enviorment with correct encoding 在docker環境下,wicket web application 編碼錯誤的問題

使用letsEncrypt替換docker容器內的nginx https憑證 using cerbot for nginx on oracle linux 9

testing gitlab and jenkins CI/CD on docker-1 在docker架設gitlab, jenkins 測試CI/CD pipeline第一章

intellij IDEA git設定說明 whenever using git push fuction in the intellij IDEA

specific instructions to create a maven archetype from local existing project. Generate an archetype from the project

openssl package update issue caused by cve-2022-2068 centos7 is at maintenance support phase2, only critical impact security issues will be patched

隨機好文

在debian9使用apt-key add gpg key from ubuntu keyserver

更新程式取消google recaptcha改用輸入驗證碼 update cnclibs to 0.0.8.6

在apache http server停用TLS 1.0/1.1 and SSL 2.0/3.0 How to disable outdated versions of SSL/TLS on Apache

如何在ubuntu 18.04上設定一開機就啟動virtualbox某個vm a way to setup ubuntu18.04 for start vm on boot

更新程式環境到wildfly18+openjdk11-phase1: upgrade mongodb server 更新程式環境到wildfly18+openjdk11-phase1: upgrade mongodb server to version 3.6