Skip to content

InCommon CA Change

Last updated: November 18, 2026
Audience: IT Staff / Technical
InCommon certificates obtained from UWIT between July 17 and November 13, 2026 need to be replaced. After November 30th, 2026, users will be unable to reach websites and applications that use those certificates.

On this page

Browser and operating system vendors are withdrawing trust from emSign certificates, emSign being the Certificate Authority (CA) behind InCommon’s former vendor, CertiNext. InCommon now issues certificates through a new CA, SSL.com. If you requested an InCommon certificate through UWIT between July 17 and November 13, 2026, they were issued by emSign; as a result, you need to replace them by November 30th, 2026 with new, SSL.com-issued certificates.

Your existing ACME account already issues SSL.com certificates – you don’t need a new account or new credentials. In most cases, one forced renewal fixes it.

Key dates

Date What happens What it means for you
Nov 13, 2026 All InCommon ACME accounts switched to issuing SSL.com certificates Any certificate you request or renew now comes from SSL.com
Nov 16, 2026 Microsoft removed support for all emSign certificates Any emSign certificate still in use will fail for Microsoft users
Nov 16, 2026 Google stops supporting new emSign certificates No new emSign certificates can be issued
Nov 30, 2026 Apple removes support for all emSign certificates Deadline: any emSign certificate still in use will fail for Apple users
Mar 15, 2027 InCommon certificate lifetime drops from 200 days to 100 days Renewals happen twice as often; manual renewal stops being practical

What you need to do

Complete these steps before November 30, 2026. Steps 1 and 2 apply to everyone; steps 3 through 5 apply only if they match your setup.

  1. Force-renew your certificates. A normal scheduled renewal won’t happen in time, because your current certificates aren’t close enough to expiring. Force a renewal of each certificate and your existing ACME account will return an SSL.com certificate; refer to How to force-renew below. Test with one certificate first, then renew the rest.
  2. Make sure each service loads the new certificate. Confirm your deploy hook or distribution script copies the new files into place, then reload or restart the service (for example, Apache or Nginx). Then confirm the live service shows an SSL.com chain.
  3. Be ready to prove domain ownership. SSL.com requires domain control validation (DCV) again for every domain. UWIT has validated the major domains, such as uw.edu and washington.edu. If you use a domain outside those, such as yourproject.org, your ACME request must pass an HTTP-01 or DNS-01 challenge. Campus IT staff have shared scripts and approaches on the Community resources wiki page.
  4. If you or your customers pin certificates, update the trust chain. Systems that keep their own list of trusted roots or intermediates must add the SSL.com chain, or they’ll reject the new certificates. Refer to the InCommon certificate chain (PDF, markdown) and add it to your trust store.
  5. If you publish DNS CAA records, add ssl.com. Once you publish any CAA record, only the CAs you list can issue certificates for your domain. Add a CAA record for ssl.com. If you don’t publish CAA records, no action is needed; that’s true for most uw.edu and washington.edu domains.

How to force-renew

Use the below commands that pertain to your ACME client. Replace anything in angle brackets with your own values, and leave out the angle brackets themselves.

certbot (Linux), one certificate:

certbot renew –force-renewal –cert-name <certificate-name>

If you originally used –config-dir or –work-dir, add them with the same paths. Otherwise, leave them out.

certbot, all certificates on the server:

certbot renew –force-renewal

simple-acme / win-acme (Windows), one certificate:

wacs.exe –renew –force –friendlyname “<friendly-name>”

simple-acme / win-acme, all certificates:

wacs.exe –renew –force

Other ACME clients (acme.sh, Posh-ACME and others): use that client’s force-renew option. Your existing account settings will issue an SSL.com certificate.

Changing key type at the same time? If you’re switching key types, for example from ECDSA to RSA, update each certificate’s renewal configuration first, then force-renew. This step is optional: SSL.com issues both RSA and ECDSA certificates.

Check which CA issued your certificate

In short, if a certificate’s chain:

  • contains emSign, replace that certificate.
  • contains SSL.com, no action is needed.

Checking a site from a web browser

Go to the website, select the padlock or site information icon (typically in/near the address bar), and view the certificate details. Check the issuer and the top of the certificate hierarchy.

Checking a certificate file on a web server

For example, certbot’s fullchain.pem:

openssl crl2pkcs7 -nocrl -certfile <path-to>/fullchain.pem | openssl pkcs7 -print_certs -noout

This lists the subject and issuer of every certificate in the file. An affected certificate shows an issuer line such as CN = emSign Root TLS CA – G1.

To confirm the service picked up the new certificate:

openssl s_client -connect <hostname>:443 -servername <hostname> -showcerts </dev/null

Note: certbot’s fullchain.pem contains your certificate and the intermediate, but not the root. Most web servers don’t need the root. Some applications want the complete chain including the root; for those, get it from the InCommon certificate chain (PDF, markdown).

Frequently asked questions

My certificate was issued by Sectigo before July 17, 2026. Do I need to replace it?

No. The November 30 deadline applies only to certificates issued by emSign. Sectigo-issued InCommon certificates stay valid until they expire. Renew them as usual when they come due, and the renewal will come from SSL.com.

Do I need a new ACME account or new credentials?

No. UWIT moved every existing InCommon ACME account to SSL.com. Keep using your current key ID, HMAC key and server URL.

Why does my new certificate say Domain Validated (DV) instead of Organization Validated (OV)?

SSL.com currently issues InCommon certificates as Domain Validated. OV will become the default again once SSL.com supports it. No action is needed: a DV certificate secures connections exactly as an OV certificate does.

Can I still get ECDSA certificates?

Yes. SSL.com issues both RSA and ECDSA certificates.

What else is changing?

On March 15, 2027, InCommon certificate lifetime drops from 200 days to 100 days. If you still renew any certificates by hand, now is a good time to automate them. Also plan to handle domain validation yourself: UWIT’s automatic validation of UW domains is a transition aid, and it may not be available in the future.

Get help

The UWIT Identity and Access Management (IAM) team can help with renewals, domain validation, and applications that reject the new certificates. Contact UWIT, mentioning the InCommon CA migration along with the following details:

  • The certificate’s common name (CN) and any subject alternative names (SANs)
  • The ACME client you use (for example, certbot or simple-acme)
  • The exact error message, plus any relevant log output (for certbot, /var/log/letsencrypt/letsencrypt.log)

Tell us right away if an application or device no longer trusts your current certificate. We’ll make sure you can get an SSL.com certificate quickly, and escalate to the vendor if needed.