Posted on 11-29-2020 09:40 PM
We use a custom domain for our JSS (even though it it hosted on JamfCloud) due to it previously being migrated from a self-hosted JSS.
The certificate for our JSS appears to have become invalid at some point today.
We're unable to log into the JSS admin console, and I am unable to run any policy.
We cannot even bypass the warning, due to HTTP Strict Transport Security (HSTS).
I've confirmed that our custom domain name still has the expected CNAME record pointing to <our_sub_domain_here>.jamfcloud.com and the cert is for *.jamfcloud.com
and expiring in 1 year, leading me to think it was just renewed by Jamf today, but incorrectly:
NET::ERR_CERT_COMMON_NAME_INVALID
Subject: *.jamfcloud.com
Issuer: Amazon
Expires on: Nov 28, 2021
Current date: Nov 29, 2020
Is anyone else experiencing a similar issue?
Posted on 11-29-2020 10:10 PM
The issue seems to have resolved itself...
I'll follow up here if I get an interesting answer from Jamf support.
Posted on 11-30-2020 09:26 AM
I've been told I just happened to catch our JSS in the middle of a scheduled cert renewal.