Posted on 09-06-2022 11:53 AM
Hello Jamf Nation,
Today we are releasing Jamf Pro 10.41. To learn more about this release and the product issues it addresses, review the release notes here.
Cloud Upgrade Schedule
Your Jamf Pro server, including any free sandbox environments, will be updated to Jamf Pro 10.41 based on your hosted data region below.
Review this guide if you need assistance identifying the Hosted Data Region of your Jamf Cloud instance.
Hosted Region |
Begins |
Ends |
ap-southeast-2 |
16 September at 1400 UTC |
16 September at 2300 UTC |
ap-northeast-1 |
16 September at 1500 UTC |
17 September at 0100 UTC |
eu-central-1 |
16 September at 2200 UTC |
17 September at 0800 UTC |
eu-west-2 |
16 September at 2300 UTC |
17 September at 0600 UTC |
us-east-1-sandbox/us-west-2-sandbox |
17 September at 0000 UTC |
17 September at 0900 UTC |
us-east-1 |
17 September at 0400 UTC |
17 September at 1700 UTC |
us-west-2 |
17 September at 0700 UTC |
17 September at 2000 UTC |
Posted on 09-17-2022 03:38 AM
Hi Justin,
We are getting Jamf notification "Verification of SSL certificates is disabled" after upgrading Jamf Pro version 10.41.x
Just for your information current "SSL Certificate Verification" by default settings set to "Always except during enrollment".
Please suggest what action we need to take.
Thanks and Regards,
Sharad Raut
+91 9850551919
Posted on 09-19-2022 09:16 AM
Hey Sharad,
Thanks for reaching out, the error message you are receiving is due to Jamf Pro deprecating the use of self-signed certificates for Tomcat, as mentioned per the Jamf Pro 10.41 release notes
Another link for further information:
If these resources don't answer your current questions emailing success@jamf.com to discuss further would be your best bet.
- Justin
Posted on 09-19-2022 05:07 PM
I'm getting this error on our cloud-based instance of Jamf Pro. The release notes clearly state:
"Customers with Cloud-hosted environments and those with a verified third-party certificate will see no changes."
Yet, I'm getting this error from our cloud-hosted environment which is configured with the recommended setting. The only thing that's changed is that our instance was switched to v10.41 over the weekend.
Posted on 09-21-2022 07:23 AM
Thank you for bringing this to our attention, by default all Jamf Cloud customers have a publicly trusted SSL. For Cloud customers to best resolve this issue it is recommended to change the “SSL Certificate Verification” setting to “Always”
In Jamf Pro > Settings > Computer Management > Security
For more information, please refer to the Safely Configuring the SSL technical article:
https://docs.jamf.com/technical-articles/Safely_Configuring_SSL_Certificate_Verification.html#concep...
For on-premise customers a trusted 3rd Party Certificate is recommended.
If these recommendations have been met for your environment and you are still running into issues please open a ticket with our Technical Support team.
Posted on 09-20-2022 08:32 AM
I'm seeing the same notification on our Cloud-hosted environment....
Posted on 09-29-2022 03:07 PM
@JustinV - Thank you for the updated information. That resolved our problem.