-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target #493
Comments
SSL/TLS support is under development. Check #392 |
In that case, why does importing the certificates from my distribution's OpenJDK into On the other hand, copying |
@urzds I'm no expert on managing the certificates used by Java but maybe adding |
https://blogs.oracle.com/gc/unable-to-find-valid-certification-path-to-requested-target fixed this issue for me. |
I just to add to the above, I would suggest doing this as I still had problems when I followed the above steps, but I could fix the issue doing the below:
I think we need to patch both the JDK and JRE folders - any security experts who might want to help me out here? |
First of all import you'r crt file into {JAVA_HOME}/jre/security/cacerts, if you still faced with this exception, change you'r jdk version. For example from |
I am closing this ticket. I understand the ticket has been resolved already. If there is anything open for you on a recent Java/GraalVM version, please feel free to reopen with new information (and ideally a reproducer for us). |
SSL connections appear to be broken in GraalVM:
I found
SSLPoke.class
on this page: https://confluence.atlassian.com/kb/unable-to-connect-to-ssl-services-due-to-pkix-path-building-failed-779355358.htmlThe problem also affects other Java applications, like Leiningen, which are unable to connect to any SSL secured web servers.
I also tried to copy over the system keystore, as described in Oracle's Java documentation, keeping the default keystore password, but without effect:
The text was updated successfully, but these errors were encountered: