← Actalis cases
Bugzilla #1670861 Delayed Revocation

Actalis: delayed revocation related to inaccurate value in stateOrProvinceName

RESOLVED FIXED Actalis
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

This case concerns Actalis revoking one certificate later than the Baseline Requirements allowed. Actalis stated that it had to grant its customer a delay of a few days in revoking one particular certificate (out of 20) rather than revoking within 5 days. Actalis attributed the delay to the practical difficulty for the customer to replace that single certificate within the 5-day window, and said it found no meaningful security risks associated with the inaccurate (but not misleading) value of stateOrProvinceName. Actalis said it was implementing measures to reduce the likelihood and extent of future revocation delays, including promoting automation of certificate enrollment and adoption of ACME, and adding CPS warnings and clarifications discouraging invalid reasons to delay revocation. In follow-up, Mozilla asked for an update on CPS currency and Actalis confirmed the most recent CPS version and that clarifications/warnings were inserted. Actalis later reported progress toward ACME adoption, including major customers using ACME, positive feedback from other customers, and a testing phase. The bug is marked RESOLVED with resolution FIXED.

Model: gpt-5.4-nano Generated: 2026-06-13 21:25 UTC Revised: 2026-06-16 18:05 UTC Confidence: 0.90 7 comments
Chronology
  1. Actalis disclosed a delayed revocation incident involving one certificate that was revoked a few days later than allowed.
  2. Actalis confirmed its CPS version and that clarifications/warnings were added.
  3. Actalis provided an update on ACME automation progress and planned measures to support adoption.
  4. Mozilla indicated intent to close the bug around 27-Jan-2021 unless issues remained.
Thread Activity
  1. Staff representative — Actalis reported that it delayed revocation by a few days for one certificate (out of 20) due to customer replacement difficulty and the lack of meaningful security risk from an inaccurate stateOrProvinceName value, and described remediation steps including ACME promotion and CPS clarifications.
  2. Mozilla representative — Mozilla asked whether Actalis had a more current CPS than Version 5.8 dated Oct 05, 2020.
  3. Staff representative — Actalis replied that Version 5.8 was the most recent and that clarifications and warnings were inserted in section 1.4.2.
  4. Community commenter — Mozilla requested an update on automation and asked for concrete steps to ensure automation adoption prevents future delays.
  5. Staff representative — Actalis provided an update that some major customers already obtain certificates via ACME, that other customers gave positive feedback, and that testing with some customers was planned.
  6. Community commenter — Mozilla acknowledged progress and suggested additional concrete actions such as monitoring the percentage of automated issuance and assessing customer-level adoption.
  7. Mozilla representative — Mozilla stated it would close the bug on or about 27-Jan-2021 unless issues still needed addressing.
Participants
Staff representative Mozilla representative Community commenter
Related Bugzilla IDs Mentioned
Similar Local Cases
#1651651 RESOLVED Delayed Revocation Opened 2020-07-09 · Closed 2023-02-22 · 100% similar
Actalis: Failure to revoke within 7 days: OCSP EKU issue
#1718554 RESOLVED Delayed Revocation Opened 2021-06-28 · Closed 2023-02-22 · 100% similar
Actalis: Delayed revocation of non-BR-compliant CA Certificate within 7 days
#1887941 RESOLVED Delayed Revocation Opened 2024-03-26 · Closed 2024-06-01 · 88% similar
Actalis: revocation delay for certificates issued with invalid RDN Order
#1572638 RESOLVED Delayed Revocation Opened 2019-08-09 · Closed 2023-02-22 · 86% similar
Actalis: Failure to revoke certs within the BR required timeframe
#1707229 RESOLVED Delayed Revocation Opened 2021-04-23 · Closed 2023-02-22 · 76% similar
SECOM: Delayed Revocation of non-technically constrained FUJIFILM Certificates
#1688844 RESOLVED Delayed Revocation Opened 2021-01-26 · Closed 2023-02-22 · 76% similar
NetLock: Delayed revocation report connected to ticket 1680378
#1656487 RESOLVED Delayed Revocation Opened 2020-07-31 · Closed 2023-02-22 · 76% similar
Izenpe: Failure to revoke within 5 days
#1636339 RESOLVED Delayed Revocation Opened 2020-05-08 · Closed 2023-02-22 · 76% similar
Entrust: Failure to revoke a certificate

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

Confirm action