← Open Access Technology International, Inc. (OATI) cases
Bugzilla #2041774 Ca Certificate Compliance Incident Self Reported Incident Repository Issue Policy Document Issue

OATI incident report: AIA CA Issuer field pointed to a PEM-encoded file instead of DER

RESOLVED FIXED Open Access Technology International, Inc. (OATI)
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 is OATI’s incident report about an Authority Information Access (AIA) CA Issuer pointer in OATI TLS certificates resolving to a PEM-encoded file instead of the DER-encoded format required by RFC 5280. OATI said it became aware of the issue on 2026-04-29 and republished the issuer certificate files in DER format on 2026-05-21. The report states that certificate issuance was not paused because the problem was limited to the externally hosted issuer file and did not affect certificate contents, validation, key material, or revocation status information. OATI later added root-cause detail and action items covering internal instructions, encoding verification, incident-response timeliness, and monitoring of public incident reports. By 2026-08-05, OATI said all action items were complete and requested closure, and CCADB issued a final call for comments on 2026-08-06. The case was resolved with FIXED.

Model: gpt-5.4-mini Generated: 2026-06-13 21:07 UTC Revised: 2026-08-16 06:01 UTC Confidence: 0.98 17 comments
Chronology
  1. OATI published the Server Issuing CA 2025 issuer certificate file.
  2. OATI became aware that the AIA CA Issuer pointer referenced a PEM-encoded file instead of DER.
  3. OATI republished the issuer certificate files in DER format.
  4. OATI stated that all action items were complete and requested closure.
Thread Activity
  1. Oati representative — OATI filed a full incident report describing the PEM-encoded AIA CA Issuer file, the remediation, and the timeline.
  2. Community commenter — A community member questioned the timeliness of OATI’s handling and reporting.
  3. Oati representative — OATI added more root-cause detail, including incomplete internal instructions, no encoding verification process, and no continuous-improvement process.
  4. Oati representative — OATI said it first became aware when the issue was posted on Bugzilla and acknowledged the gap between responses and the solution.
  5. Oati representative — OATI updated its action items, including automated monitoring/alerting and incident-response improvements.
  6. Oati representative — OATI reported completion of the monitoring/alerting and incident-review action items, with incident-response process work still ongoing.
  7. Oati representative — OATI said the remaining incident-response process action item was completed on 2026-07-28.
  8. Oati representative — OATI posted a closure summary stating that the issuer files were replaced with DER files and all action items were completed.
  9. CCADB representative — CCADB issued a final call for comments or questions and said the report would otherwise be closed around 2026-08-13.
Participants
Oati representative Community commenter CCADB representative
Related Bugzilla IDs Mentioned
Similar Local Cases
#2032482 RESOLVED Ca Certificate Compliance Incident Certificate Misissuance Problem Reporting Failure Opened 2026-04-16 · Closed 2026-07-30 · 97% similar
OATI: Misissuance detected by PKIMetal
#2032468 RESOLVED Ca Certificate Compliance Incident Self Reported Incident Certificate Misissuance Opened 2026-04-16 · Closed 2026-08-09 · 86% similar
VISA: Misissuance detected by PKIMetal
#1967929 RESOLVED Incident Opened 2025-05-22 · Closed 2025-07-17 · 85% similar
KIR: Failed to respond a Certificate Problem Report within 24 hours
#2052541 ASSIGNED Incident Problem Reporting Failure Delayed Revocation Remediation Tracking Opened 2026-07-03 Still Open · 83% similar
NETLOCK: Failure to Respond to a Certificate Problem Report Within 24 Hours
#2066649 RESOLVED Incident Self Reported Incident Problem Reporting Failure Remediation Tracking Opened 2026-08-26 · Closed 2026-10-05 · 82% similar
Microsoft PKI Services: Missed Seven-Day Update for Bugzilla 2059818
#2065157 RESOLVED Ca Certificate Compliance Incident Self Reported Incident Delayed Revocation Opened 2026-08-20 · Closed 2026-09-28 · 81% similar
SwissSign: Delayed revocation in Bug 2057448
#2053948 RESOLVED Ca Certificate Compliance Self Reported Incident Ccadb Disclosure Issue Incident Opened 2026-07-09 · Closed 2026-10-02 · 81% similar
IdenTrust: Delayed disclosure of Intermediate CA in CCADB
#2073548 RESOLVED Ca Certificate Compliance Incident Externally Reported Incident Problem Reporting Failure Opened 2026-09-18 · Closed 2026-10-21 · 80% similar
Sectigo: Submitted CPR not replied to within 24 hours

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

⚠

Confirm action