フィルタリング: intermediate CA certificates x 消去
new

DigiCert moving to new G5 root and intermediate CA certificates

On March 8, 2023, at 10:00 MST (17:00 UTC), DigiCert will begin updating the default public issuance of TLS/SSL certificates to new, public, fifth-generation (G5) root and intermediate CA (ICA) certificate hierarchies.

TLS/SSL certificate brands:

  • DigiCert Basic, Secure Site, and Secure Site Pro OV and EV
  • GeoTrust DV, OV, and EV
  • Thawte DV, OV, and EV
  • RapidSSL DV
  • Encryption Everywhere DV

For more information, see our DigiCert G5 Root and Intermediate CA Certificate Update knowledge base article. We recommend you bookmark this page, as we will continue to update this article as new information, ICA certificates, and cross-signed roots become available.


Why is DigiCert moving to new root and intermediate certificates?

The industry now requires Certificate Authorities (CAs) to stop using multipurpose roots and ICA certificates and start using single-purpose certificates instead.

This means:

  • Each new DigiCert single-purpose G5 root chains to a single-purpose ICA certificate.
  • Each new single-purpose G5 ICA certificate only issues a single type of end-entity certificate.

For example, DigiCert has a single-purpose G5 root and ICA certificate for issuing RSA TLS/SSL certificates and another a single-purpose G5 root and ICA certificate for issuing ECC TLS/SSL certificates.

For more information about moving to single-purpose root and ICA certificates, see Mozilla's CA/Prioritization.


How do new root and intermediate CA certificates affect me?

From March 8, 2023, DigiCert will issue new public TLS/SSL certificates from the new G5 root and ICA certificate dedicated hierarchies. At this time, no action is required* unless you do any of the following:

  • Pin root or ICA certificates
  • Hard-code the acceptance of root or ICA certificates
  • Operate a trust store

We recommend updating your environment before March 8, 2023. Stop pinning or hard-coding root or ICA certificate acceptance and distribute DigiCert G5 roots to the local trust stores to ensure TLS/SSL certificates that chain up to the new root certificates are trusted.


How do the new G5 root and ICA certificates affect my existing TLS/SSL certificates?

Rolling out new root and intermediate CA (ICA) certificates does not affect existing TLS/SSL certificates. We don't remove old ICA and root certificates from certificate stores until all the certificates issued from them have expired. Active TLS/SSL certificates issued from a replaced root and ICA certificates remain trusted until they expire.

However, it does affect existing TLS/SSL certificates if you reissue or duplicate them from March 8, 2023. DigiCert will issue all new TLS/SSL certificates from the new G5 root and ICA certificate chains, including reissues and duplicates.


*Installing a cross-signed root certificate

Until our new G5 roots have the same ubiquity as the older DigiCert root certificates, we recommend installing the DigiCert-provided cross-signed root along with the intermediate CA certificate included with each TLS/SSL certificate issued from a G5 root certificate hierarchy.

Installing the cross-signed root certificate ensures your TLS certificate remains trusted even when its G5 root certificate is missing from a needed trust store.

We will add a link to instructions for installing a cross-signed root certificate as soon as they become available.


What if I need more time to update my environment?

If you need more time to prepare, contact DigiCert Support. We will set up your account so you can continue to use the root and ICA certificates you are using now.


Mozilla to distrust four DigiCert roots in 2024

The industry is moving to dedicated hierarchies, so the longer you stay on the old roots and ICA certificates, the less time you will have to move off them when the industry stops trusting them.

In 2024, Mozilla will distrust four DigiCert root certificates**:

  • April 2024
    • Baltimore CyberTrust Root, April 15, 2024
  • November 2024
    • DigiCert Assured ID Root CA, November 10, 2024
    • DigiCert Global Root CA, November 10, 2024
    • DigiCert High Assurance EV Root CA, November 10, 2024

If your certificates are issued from these certificate root hierarchies, you should move to new G5 root dedicated hierarchies before Mozilla distrusts your root certificate.

**TLS/SSL certificates issued before these dates will remain trusted until they expire. However, certificates issued from these dates, including reissues and duplicates, will no longer be trusted.

new

CertCentral to issue GeoTrust and RapidSSL DV certificates from new intermediate CA certificates

On May 24, 2022, between 9:00 am and 11:00 am MDT (3:00 pm and 5:00 pm UTC), DigiCert will replace the GeoTrust and RapidSSL intermediate CA (ICA) certificates listed below. We can no longer issue maximum validity (397-day) DV certificates from these intermediates.

Old ICA certificates

  • GeoTrust TLS DV RSA Mixed SHA256 2020 CA-1
  • GeoTrust TLS DV RSA Mixed SHA256 2021 CA-1
  • RapidSSL TLS DV RSA Mixed SHA256 2020 CA-1
  • RapidSSL TLS DV RSA Mixed SHA256 2021 CA-1

New ICA certificates

  • GeoTrust Global TLS RSA4096 SHA256 2022 CA1
  • RapidSSL Global TLS RSA4096 SHA256 2022 CA1

See the DigiCert ICA Update KB article.

How does this affect me?

Rolling out new ICA certificates does not affect your existing DV certificates. Active certificates issued from the replaced ICA certificates will remain trusted until they expire.

However, all new certificates, including certificate reissues, will be issued from the new ICA certificates. To ensure ICA certificate replacements go unnoticed, always include the provided ICA certificate with every TLS certificate you install.

No action is required unless you do any of the following:

  • Pin the old versions of the intermediate CA certificates
  • Hard code the acceptance of the old versions of the intermediate CA certificates
  • Operate a trust store that includes the old versions of the intermediate CA certificates

Action required

If you practice pinning, hard code acceptance, or operate a trust store, update your environment as soon as possible. You should stop pinning and hard coding ICA certificates or make the necessary changes to ensure your GeoTrust DV and RapidSSL DV certificates issued from the new ICA certificates are trusted. In other words, make sure they can chain up to their new ICA certificate and trusted root.

See the DigiCert Trusted Root Authority Certificates page to download copies of the new Intermediate CA certificates.

What if I need more time?

If you need more time to update your environment, you can continue to use the old 2020 ICA certificates until they expire. Contact DigiCert Support, and they can set that up for your account. However, after May 31, 2022, RapidSSL DV and GeoTrust DV certificates issued from the 2020 ICA certificates will be truncated to less than one year.

compliance

Industry moves to 3072-bit key minimum RSA code signing certificates

Starting May 27, 2021, to comply with new industry standards for code signing certificates, DigiCert will make the following changes to our code signing certificate process.

  • Stop issuing 2048-bit key code signing certificates
  • Only issue 3072-bit key or stronger code signing certificates
  • Use 4096-bit key intermediate CA and root certificates to issue our code signing certificates.

See Appendix A in the Baseline Requirements for the Issuance and Management of Publicly-Trusted Code Signing Certificates to learn more about these industry changes,

How do these changes affect my existing 2048-bit key certificates?

All existing 2048-bit key size code signing certificates issued before May 27, 2021, will remain active. You can continue to use these certificates to sign code until they expire.

What if I need 2048-bit key code signing certificates?

Take these actions, as needed, before May 27, 2021:

  • Order new 2048-bit key certificates
  • Renew expiring 2048-bit key certificates
  • Reissue 2048-bit key certificates

How do these changes affect my code signing certificate process starting May 27, 2021?

Reissues for code signing certificate

Starting May 27, 2021, all reissued code signing certificates will be:

  • 3072-bit key or stronger. See eTokens for EV code signing certificates and HSMs for EV code signing certificates below.
  • Automatically issued from new intermediate CA and root certificates. See New ICA and root certificates below.

New and renewed code signing certificates

Starting May 27, 2021, all new and renewed code signing certificates will be:

  • 3072-bit key or stronger. See eTokens for EV code signing certificates and HSMs for EV code signing certificates below.
  • Automatically issued from new intermediate CA and root certificates. See New ICA and root certificates below.

CSRs for code signing certificates

Starting May 27, 2021, you must use a 3072-bit RSA key or larger to generate all certificate signing requests (CSR). We will no longer accept 2048-bit key CSRs for code signing certificate requests.

eTokens for EV code signing certificates

Starting May 27, 2021, you must use an eToken that supports 3072-bit keys when you reissue, order, or renew an EV code signing certificate.

  • When you order or renew an EV code signing certificate, DigiCert includes a 3072-bit eToken with your purchase. DigiCert provides an eToken with the Preconfigured Hardware Token provisioning option.
  • When your reissue your EV code signing certificate reissues, you must provide your own 3072-bit eToken. If you don't have one, you will be unable to install your reissued certificate on your eToken.
  • You must have a FIPS 140-2 Level 2 or Common Criteria EAL4+ compliant device.

HSMs for EV code signing certificates

Starting May 27, 2021, you must use an HSM that supports 3072-bit keys. Contact your HSM vendor for more information.

New ICA and root certificates

Starting May 27, 2021, DigiCert will issue all new code signing certificates from our new RSA and ECC intermediate CA and root certificates (new, renewed, and reissued).

RSA ICA and root certificates:

  • DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1
  • DigiCert Trusted Root G4

ECC ICA and root certificates:

  • DigiCert Global G3 Code Signing ECC SHA384 2021 CA1
  • DigiCert Global Root G3

No action is required unless you practice certificate pinning, hard code certificate acceptance, or operate a trust store.

If you do any of these things, we recommend updating your environment as soon as possible. Stop pinning and hard coding ICAs or make the necessary changes to ensure certificates issued from the new ICA certificates are trusted (in other words, they can chain up to their issuing ICA and trusted root certificates).

References

If you have questions or concerns, please contact your account manager or our support team.

enhancement

CertCentral Services API: Auto-reissue support for Multi-year Plans

We are happy to announce that the CertCentral Services API now supports automatic certificate reissue requests (auto-reissue) for Multi-year Plans. The auto-reissue feature makes it easier to maintain SSL/TLS coverage on your Multi-year Plans.

You can enable auto-reissue for individual orders in your CertCentral account. When auto-reissue is enabled, we automatically create and submit a certificate reissue request 30 days before the most recently issued certificate on the order expires.

Enable auto-reissue for a new order

To give you control over the auto-reissue setting for new Multi-year Plans, we added a new request parameter to the endpoints for ordering DV, OV, and EV TLS/SSL certificates: auto_reissue.

By default, auto-reissue is disabled for all orders. To enable auto-reissue when you request a new Multi-year Plan, set the value of the auto_reissue parameter to 1 in the body of your request.

Example request body:

Example order request body with auto reissue enabled

Note: In new order requests, we ignore the auto_reissue parameter if:

  • The product does not support Multi-year Plans.
  • Multi-year Plans are disabled for the account.

Update auto-reissue setting for existing orders

To give you control over the auto-reissue setting for existing Multi-year Plans, we added a new endpoint: Update auto-reissue settings. Use this endpoint to enable or disable the auto-reissue setting for an order.

Get auto-reissue setting for an existing order

To help you track the auto-reissue setting for existing certificate orders, we added a new response parameter to the Order info endpoint: auto_reissue. The auto_reissue parameter returns the current auto-reissue setting for the order.

new

ICA certificate chain selection for public DV flex certificates

We are happy to announce that select public DV certificates now support Intermediate CA certificate chain selection:

  • GeoTrust DV SSL
  • Thawte SSL 123 DV
  • RapidSSL Standard DV
  • RapidSSL Wildcard DV
  • Encryption Everywhere DV

You can add a feature to your CertCentral account that enables you to control which DigiCert ICA certificate chain issues the end-entity certificate when you order these public DV products.

This feature allows you to:

  • Set the default ICA certificate chain for each supported public DV certificate.
  • Control which ICA certificate chains certificate requestors can use to issue their DV certificate.

Configure ICA certificate chain selection

To enable ICA selection for your account:

  1. Contact your account manager or our Support team.
  2. Then, in your CertCentral account, in the left main menu, go to Settings > Product Settings.
  3. On the Product Settings page, configure the default and allowed intermediates for each supported and available DV certificate.

For more information and step-by-step instructions, see the Configure the ICA certificate chain feature for your public TLS certificates.

new

DigiCert Services API: DV certificate support for ICA certificate chain selection

In the DigiCert Services API, we made the following updates to support ICA selection in your DV certificate order requests:

Pass in the issuing ICA certificate's ID as the value for the ca_cert_id parameter in your order request's body.

Example DV certificate request:

Example DV TLS certificate request

For more information about using ICA selection in your API integrations, see DV certificate lifecycle – Optional ICA selection.

compliance

デジサートは SHA-1 コードサイニング証明書の発行を停止

 2020年12月1日(火) MST,デジサートは SHA-1 コードサイニングと SHA-1 EV コードサイニング証明書のハック尾を停止予定です。

注記:すべての既存の SHA-1 コードサイニング/EV コードサイニング証明書は、有効期限が切れるまでそのまま有効になります。

デジサートではなぜ、このような変更を行うのですか?

新しい業界基準に準拠するため、認証局 (CA) は、2021年1月1日までに次の変更を実施する必要があります。

  • SHA-1 コードサイニング証明書の発行を停止する
  • SHA-1 中間 CA と SHA-1 ルート証明書の発行を停止し、SHA-256 アルゴリズムコードサイニングとタイムスタンプ証明書を発行する

パブリックトラストコードサイニング証明書の発行と管理のベースライン要件付録 A を参照してください。

SHA-1 コードサイニング証明書の変更は、私にどのような影響がありますか?

SHA-1 コードサイニング証明書に依拠する場合、2020年12月1日までに必要に応じて、次の対応を行ってください。

  • 新しい SHA-1 証明書を取得する
  • SHA-1 証明書を更新する
  • 必要な SHA-1 証明書を再発行および取得する

2020年12月1日の変更に関する詳細は、 ナレッジベースの記事 「デジサートは SHA-1 コードサイニング証明書の発行を停止する」 を参照してください。

他に質問がある場合は、アカウントマネージャまたは サポートチーム にお問い合わせください。.

new

デジサートを複数の中間 CA 証明書と入替

11月2日、デジサートは別のセットの中間 CA 証明書 (ICA) を入れ替えます。入れ替える ICA 証明書のリストについては、「DigiCert ICA 更新 KB 記事」 を参照してください。

どのような影響がありますか?

新しい ICA を始動することで、既存の証明書が影響を受けることはありません。すべての発行済証明書の有効期限が切れるまで、証明書ストアから古い ICA を削除することはありません。これは、入れ替えた ICA から発行された有効な証明書が引き続き信頼できることを意味します。

ただし、新しい ICA から発行されているため、それらを再発行すると、既存の証明書に影響を及ぼします。インストールするべての証明書に、所定の ICA を必ず含めることをお勧めします。これは、ICA 入替が通知なしで行われるようにするため、常に推奨するベストプラクティスです。

以下のいずれかを実行しないかぎり、特に操作は必要ありません。

  • 中間認証局証明書の旧バージョンをピン留めする
  • 中間認証局証明書の旧バージョンの受け入れをハードコーディングする
  • 中間認証局証明書の旧バージョンを含むトラストストアを運営する

上記のいずれかを実行するばあい、現在の環境をできるかぎり早い段階で更新することをお勧めします。ICA の ピンニングを停止およびハードコーディングを停止するか、ICA から発行されれた証明書が信頼されるように必要な変更を行ってください (すなわち、更新した ICA とトラストルーツまでチェーンできます)。

中間 CA 証明書の入替

下記のページは必ず、モニタリングしてください。これらは有効なページで、ICA 証明書入替情報と新しいデジサートの中間 CA 証明書のコピーとともに、定期的に更新されます。

デジサートはなぜ、中間 CA 証明書を入れ替えるのですか?

次の目的で ICA の入替を行います。

  • ICA 入替でお客様のアジリティを促進する。
  • 証明書発行の範囲を所定の ICA から削減し、業界基準および CA/Browser Forum ガイドラインでの変更による、中間およびエンドエンティティ証明書への影響を緩和する、
  • ICA が最新の改善をベースに作動できるように、インターネットのセキュリティを改善する。

質問や懸念事項がある場合は、マネージャまたは サポートチーム までお問い合わせください。

new

パブリック OV と EV フレックス証明書用 ICA 証明書チェーンの選択

フレックス証明書付きパブリック OV と EV 証明書は現在、中間 CA 証明書チェーンの選択をサポートしていることをお知らせいたします。

どの DigiCert ICA 証明書チェーンがパブリック OV および EV "フレックス" 証明書を発行するかを管理できるオプションを CertCentral アカウントに追加することができます。

このオプションでは次のことが可能です。

  • デフォルト ICA 証明書チェーンを各パブリック OV および EV フレックス製品向けに設定します。
  • 証明書要求者がどの ICA 証明書チェーンを使用してフレックス証明書を発行するか管理します。

ICA 証明書チェーンの選択を構成する

お使いのアカウントについて ICA 選択を有効にするには、アカウントマネージャまたは サポートチーム にお問い合わせください。次に、製品設定ページの CertCentral アカウント(左メインメニューで [設定] >[製品設定] の順に進む) で OV と EV フレックス証明書の各タイプについて、デフォルトおよび許可された中間証明書を構成します。

詳細およびステップ別の手順は、「パブリック OV と EV フレックス証明書の ICA 証明書チェーンオプション」 を参照してください。

new

DigiCert Services API は ICA 証明書チェーンの選択をサポート

DigiCert Services API では、お使いの API 統合で ICA 選択をサポートするため、次の更新を行いました。

  • 新規作成済 製品制限エンドポイント
    このエンドポイントを使用して、お使いのアカウントの各管理グループについて有効になった製品の制限と設定に関する情報を取得します。こには、各製品のデフォルトおよび許可された ICA 証明書チェーンの ID 値が含まれます。
  • パブリック TLS OV と EV フレックス証明書オーダー要求への ICA 選択のサポートを追加
    製品について許可された中間証明書を構成した後、API を使用してオーダー要求を提出するときに証明書を発行する ICA 証明書チェーンを選択することができます。
    発行 ICA 証明書の ID をオーダー要求本文の ca_cert_id パラメータ用の値にパスします。

フレックス証明書要求の例:

Example flex certificate request

API 統合の ICA 選択についての詳細は、「OV/EV 証明書の使用期間 – (オプション) ICA 選択」 を参照してください。