← BEIJING CERTIFICATE AUTHORITY Co., Ltd. cases
Bugzilla #1647181 Root Inclusion Ca Documents

BJCA root inclusion request and CP/CPS review for BJCA Global Root CA1 and CA2

RESOLVED FIXED BEIJING CERTIFICATE AUTHORITY Co., Ltd.
This summary was auto-generated by AI and revised by me when needed — accuracy improves with each update. Always refer to the official Bugzilla thread as the authoritative source. If you spot an inaccuracy, let me know via the contact form.
AI Summary

BEIJING CERTIFICATE AUTHORITY Co., Ltd. requested Mozilla Root Store inclusion for BJCA Global Root CA1 and BJCA Global Root CA2, and attached its point-in-time audit report and BR self-assessment. Mozilla reviewed BJCA’s CP/CPS and asked for clarifications and revisions on items including email verification, naming, wildcard validation language, EV address verification, and subscriber agreement/request signature verification. BJCA published updated CP/CPS versions in response, including v1.0.3, v1.0.4, v1.0.6, and later provided additional audit and self-assessment materials. Public discussion started on 2022-11-30, Mozilla later recommended approval, and on 2023-03-16 Mozilla approved inclusion of the two roots with EV enabled. The thread also records a later check of BJCA test websites for the roots, after which BJCA said the sites had been checked and remediated. The bug is resolved as FIXED.

Model: gpt-5.4-mini Generated: 2026-06-13 21:22 UTC Revised: 2026-06-16 18:16 UTC Confidence: 0.98 40 comments
Chronology
  1. BJCA requested Mozilla Root Store inclusion for BJCA Global Root CA1 and BJCA Global Root CA2.
  2. BJCA published BJCA Global CP/CPS v1.0.3 in response to Mozilla comments.
  3. BJCA published BJCA Global CP/CPS v1.0.6 after further Mozilla review comments.
  4. Public discussion began for the inclusion request.
  5. Mozilla approved inclusion of BJCA Global Root CA1 and BJCA Global Root CA2 with EV enabled.
  6. BJCA said it had checked and remediated the test websites.
Thread Activity
  1. Bjca representative — BJCA opened the case, requested root inclusion, and linked its audit report, BR self-assessment, and CCADB case information.
  2. Mozilla representative — Mozilla asked BJCA for evidence of its address and said the CPS would need stronger email verification language.
  3. Bjca representative — BJCA provided address details and said it would revise the CPS based on Mozilla feedback.
  4. Mozilla representative — Mozilla posted a detailed CPS review with items marked good and items needing fixes.
  5. Bjca representative — BJCA said it had published BJCA Global CP/CPS v1.0.3 to address Mozilla’s comments.
  6. Bjca representative — BJCA announced BJCA Global CP/CPS v1.0.4 and said section 4.9.12 now specified how third parties demonstrate private key compromise.
  7. Bjca representative — BJCA reported completion of its annual WebTrust audit and provided seal links.
  8. Mozilla representative — Mozilla asked BJCA to provide the current English CP and CPS URLs more directly.
  9. Mozilla representative — Mozilla said BJCA’s CPS v1.0.3 revisions addressed the review comments and that the matter could proceed to public discussion.
  10. Mozilla representative — Mozilla announced that public discussion had started and expected to close around 2023-01-11.
  11. Mozilla representative — Mozilla attached BJCA’s compliance self-assessment and responses to Root Inclusion Considerations.
  12. Mozilla representative — Mozilla concluded public discussion and recommended approval, starting a one-week last-call period.
  13. Mozilla representative — Mozilla asked BJCA for reasons not to apply top-level-domain restrictions.
  14. Bjca representative — BJCA said it hoped not to implement such restrictions and explained its reasons.
  15. Mozilla representative — Mozilla approved inclusion of BJCA Global Root CA1 and BJCA Global Root CA2 and said NSS and PSM bugs would be filed for the changes.
  16. Mozilla representative — Mozilla asked BJCA to check test websites because of inconsistent chaining behavior.
  17. Bjca representative — BJCA said it had checked and remediated the test websites.
Participants
Bjca representative Mozilla representative
Related Bugzilla IDs Mentioned
Similar Local Cases
#1554846 RESOLVED Root Inclusion Cp Cps Document Opened 2019-05-28 · Closed 2024-04-12 · 81% similar
Add iTrusChina root certificate(s)
#1102143 RESOLVED Ca Certificate Root Program Ca Documents Opened 2014-11-20 · Closed 2022-11-14 · 80% similar
Add Renewed Autoridad de Certificacion Firmaprofesional root certificate
#1710831 RESOLVED Ca Certificate Root Program Root Inclusion Opened 2021-05-12 · Closed 2023-08-01 · 79% similar
Add LAWtrust Root CA2 to NSS
#1313982 RESOLVED Ca Certificate Root Program Root Inclusion Opened 2016-10-31 · Closed 2025-04-02 · 78% similar
Add SECOM root certificates
#1688854 RESOLVED Root Inclusion Opened 2021-01-26 · Closed 2023-11-30 · 77% similar
Add TrustAsia root certificates
#1799533 RESOLVED Ca Certificate Root Program Root Inclusion Opened 2022-11-07 · Closed 2024-03-15 · 77% similar
Add SSL.com 2022 TLS Root CA Certificates
#1602415 ASSIGNED Root Inclusion Opened 2019-12-09 Still Open · 77% similar
Add PostSignum Root QCA 4 and PostSignum Root QCA ECC R1
#848766 RESOLVED Root Inclusion Opened 2013-03-07 · Closed 2023-02-24 · 77% similar
Add OATI's Root CA Certificate to Mozilla's trusted root list

We use only essential cookies and local browser storage for preferences and security. See our Privacy Policy for details.

Confirm action