Closed zipfch closed 6 years ago
Hi @zipfch.
The most common SSL error that comes across with JSSImporter is with Sierra and now presumably High Sierra machines not having adequate python libraries for SSL.
Have you followed the README's instructions for: python -m ensurepip --user -U && pip install -I --user pyopenssl run as the user AutoPkg is running under?
Barring that, I'm working on updates to python-jss and JSSImporter that use curl instead of python for the HTTP requests which will avoid these dependency issues.
Also, if you're using a self-signed certificate, even the curl approach is going to have issues.
At this point, indeed, let's move towards the new code to see if it helps.
You can check out the testing branch; the README includes instructions for building an installer package and/or testing by just copying the files.
I'll soon have a package already made for testing up in the releases section as a beta.
Hello,
I'm using AutoPkgr 1.4.2 (1375), AutoPkg 1.0.2 and JSSImporter 0.5.1
I made sure to check the following:
defaults read com.github.autopkg JSS_URL
defaults read com.github.autopkg API_USERNAME
defaults read com.github.autopkg API_PASSWORD
Even after disabling SSL verification in autopkg via
sudo defaults write com.github.autopkg JSS_VERIFY_SSL -bool false
, I still seem to be unable to run any recipe from the jss-recipes repository. How come this step seems to be interfering with the recipe being run through?As an example i posted the log of
sudo autopkg run AdobeFlashPlayer.jss