← HARICA cases
Bugzilla #2062162 Ca Certificate Compliance Externally Reported Incident Problem Reporting Failure Policy Document Issue Information Request

HARICA TLS server certificate issuance and CPR response dispute over duplicate DNs

ASSIGNED HARICA
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 a complaint that HARICA issued TLS server certificates with duplicate Distinguished Names that the reporter says violate HARICA’s CPS. The reporter said they raised the issue to HARICA’s Certificate Problem Report address on 2026-08-01 and initially believed HARICA did not reply for almost three days. HARICA responded that it received the CPR on 2026-08-01, sent a response three hours and forty-three minutes later, and issued its final determination on 2026-08-04 after investigation. HARICA stated that the CPR involved certificates across 13 issuing CAs and that it saw no violation of section 4.9.5 in its handling of the report. The thread does not show a resolution of the underlying duplicate-DN allegation in this bug; it focuses on whether HARICA met the CPR response and investigation requirements. The bug remains assigned to HARICA.

Model: gpt-5.4-mini Generated: 2026-08-16 08:19 UTC Confidence: 0.93 2 comments
Chronology
  1. A CPR was sent to HARICA about duplicate Distinguished Names in subscriber certificates across multiple issuing CAs.
  2. HARICA received the CPR and sent an initial response the same day.
  3. HARICA issued its final determination after completing its investigation.
Thread Activity
  1. Community commenter — The reporter alleged that HARICA’s CPS requires unique Distinguished Names and said the CPR was not answered for almost three days.
  2. HARICA — HARICA said it received the CPR, responded within three hours and forty-three minutes, completed its investigation, and saw no section 4.9.5 violation.
Participants
Community commenter HARICA
Related Bugzilla IDs Mentioned
Similar Local Cases
#2058920 ASSIGNED Problem Reporting Failure Incident Externally Reported Incident Opened By Ca Opened 2026-07-29 Still Open · 72% similar
CFCA: Delayed response to CPR related with bug 2058918
#2055539 RESOLVED Problem Reporting Failure Incident Externally Reported Incident Revocation Issue Opened 2026-07-16 · Closed 2026-08-11 · 72% similar
DigiCert: Delayed availability of OCSP responses
#2056934 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Ccadb Disclosure Issue Opened 2026-07-22 Still Open · 71% similar
Actalis: failure to timely update CP/CPS for AgID SubCAs
#2047952 RESOLVED Ca Certificate Compliance Incident Externally Reported Incident Problem Reporting Failure Opened 2026-06-16 · Closed 2026-08-04 · 71% similar
KIR: OCSP responder does not return status for precertificate
#2063842 UNCONFIRMED Ca Certificate Compliance Incident Externally Reported Incident Problem Reporting Failure Opened 2026-08-15 Still Open · 70% similar
NETLOCK: Failure to file a preliminary incident report within 72 hours (OCSP responder incident, Bug 2051459)
#2059735 ASSIGNED Ca Certificate Compliance Incident Externally Reported Incident Ccadb Disclosure Issue Opened 2026-07-31 Still Open · 70% similar
Asseco DS / Certum: Delayed publication of Full Incident Report for Bug 2055775
#2055542 ASSIGNED Ca Certificate Compliance Incident Self Reported Incident Problem Reporting Failure Opened 2026-07-16 Still Open · 70% similar
DigiCert: Delayed response to problem report related to Bug 2055539
#2052541 ASSIGNED Ca Certificate Compliance Incident Problem Reporting Failure Ccadb Disclosure Issue Opened 2026-07-03 Still Open · 70% similar
NETLOCK: Failure to Respond to a Certificate Problem Report Within 24 Hours

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

Confirm action