# Upcoming expiration of Developer ID Certification Authority (Sub-CA) — retained record

> Retained news record from news:ml-latest-news-apple-developer.

Canonical: https://highsignal.app/data/records/7cc92b395496b686

[← sources](https://highsignal.app/data)


source: [news](https://highsignal.app/data/news) (news:ml-latest-news-apple-developer)  published 2026-10-01 17:00 ingested 2026-10-24 10:04

[original source ↗](https://developer.apple.com/news/?id=w4atic4c)

## retained text



```
Upcoming expiration of Developer ID Certification Authority (Sub-CA)
October 1, 2026
The original Developer ID Certification Authority (Sub-CA) expires on February 1, 2027. Certificates issued by this authority will stop working on that date.
What to do:
- Check if you’re affected. In Certificates, Identifiers & Profiles, look for certificates expiring on or before February 1, 2027. See Replacing Developer ID certificates issued from the previous Sub-CA for help identifying your certificate’s authority.
- Create a new certificate. Generate a replacement from the current authority, Developer ID Certification Authority (G2). Note: This certificate authority is valid until 2031, but the certificates issued by the certificate authority expire annually and must be renewed each year.
- If you’re using Xcode 11.4 or earlier, update before creating your new certificate.
- When prompted for a Developer ID Certificate Intermediary, select G2 Sub-CA. Choosing another option may issue a certificate that also expires in 2027.
- Re-sign based on what you distribute.
- Installer packages (.pkg): Starting February 1, 2027, .pkg files signed with an affected certificate will no longer install. Re-sign all packages with your new certificate before this date.
- Mac apps: Previously signed and notarized Mac software (with a secure timestamp) will keep working—no action needed. For future updates, sign with your new certificate and include a secure timestamp for notarization.
```



document fetched 2026-10-24 10:04