Skip to content
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

Closed
evanH13 opened this issue Aug 11, 2020 · 6 comments
Closed

SSL Issues with OpenJDK #7

evanH13 opened this issue Aug 11, 2020 · 6 comments

Comments

@evanH13
Copy link

evanH13 commented Aug 11, 2020

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:

  1. Containerize Jamf Pro using the Jamf Dockerfile
  2. Enroll machines manually or via DEP
  3. Use the binary to run recon or policy

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

@battlecow
Copy link
Contributor

Just updated the image to 8.5.57 upstream Tomcat version, the ca-certificate package from the 8.5.51 tag is version 20190110 while the new tag is version 20200601~deb10u1.
Please give this new version a test and see if it resolves your certificate issue.

@evanH13
Copy link
Author

evanH13 commented Aug 12, 2020

@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.

@battlecow
Copy link
Contributor

That would be great, I just created the corretto branch so just target that one. Thanks!

@evanH13
Copy link
Author

evanH13 commented Aug 12, 2020

@battlecow Done! Let me know if you need anything else from me.

@battlecow
Copy link
Contributor

LGTM, thanks for the PR. 👍

@ahousseini
Copy link
Contributor

ahousseini commented Aug 24, 2020

There is a bug in the debian package: https://bugs.debian.org/962596
See this related issue: docker-library/tomcat#208
This workaround should work for the moment:

RUN wget --no-check-certificate -c https://www.geotrust.com/resources/root_certificates/certificates/GeoTrust_Global_CA.pem \
	&& mkdir /usr/local/share/ca-certificates/extra \
	&& mv GeoTrust_Global_CA.pem /usr/local/share/ca-certificates/extra/GeoTrust_Global_CA.crt \
	&& update-ca-certificates \
	&& rm -rf /usr/local/share/ca-certificates/extra

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants