-
Notifications
You must be signed in to change notification settings - Fork 15
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
SSL Issues with OpenJDK #7
Comments
Just updated the image to 8.5.57 upstream Tomcat version, the ca-certificate package from the 8.5.51 tag is version |
@battlecow we actually were already using 8.5.57. I ended up using a Corretto base image, I had to modify the Dockerfile to accommodate the different flavor of Linux, but that resolved our issue. I can submit a PR if you'd like. |
That would be great, I just created the corretto branch so just target that one. Thanks! |
@battlecow Done! Let me know if you need anything else from me. |
LGTM, thanks for the PR. 👍 |
There is a bug in the debian package: https://bugs.debian.org/962596
|
We recently began experiencing issues when enrolling and using the Jamf binary to execute commands and run policies. Looking at the server logs, we're seeing a large amount of SSLHandshake errors specifically with VPP and what appears to be Jamf's Patch Management system. When running recon, we receive an "Unknown error", with no additional information. Based on our Jamf logs, it looks like the SSL issue is related to OpenJDK not having the correct certificates. Can Jamf please take a look at this Docker image and explore switching to another JDK?
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The binary should work as expected.
Additional context
Sample from Jamf log:
Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
The text was updated successfully, but these errors were encountered: