A-Trust root inclusion request for A-Trust-nQual-03, Websites trust bit, and EV enablement

This case is A-Trust’s request to add the A-Trust-nQual-03 root certificate to Mozilla’s trusted list and enable the Websites trust bit, later expanded to include EV. The request was opened by A-Trust after it said it had completed its WebTrust CA audit and would provide the final report and management assertion. Mozilla requested additional documentation and translations of the CP/CPS sections covering organization verification, domain control, OCSP behavior, and EV policy details. A-Trust provided translated excerpts, updated its EV CP/CPS, fixed the test website’s intermediate certificate delivery, and clarified the OCSP documentation. Mozilla then opened public discussion, later approved the request, and filed follow-up NSS and PSM bugs to make the changes. The bug was resolved as FIXED.

1. 2009-11-24 A-Trust requested inclusion of the A-Trust-nQual-03 root certificate in Mozilla’s trusted list.
2. 2011-02-07 A-Trust asked to include EV in the same root inclusion request.
3. 2011-03-14 Mozilla opened the first public discussion period for the request.
4. 2011-06-02 Mozilla approved inclusion of A-Trust-nQual-03 with Websites trust and EV enabled.

1. 2009-11-24 A-trust representative — A-Trust said it had finished the WebTrust CA program audit and provided CP/CPS links and the certificate hierarchy.
2. 2009-11-30 Mozilla representative — Mozilla started the information gathering and verification phase.
3. 2010-03-09 A-trust representative — A-Trust attached answers to the information gathering document and pointed to the WebTrust seal.
4. 2010-03-17 A-trust representative — A-Trust clarified the SSL hierarchy and provided translated CPS text for domain and organization verification.
5. 2011-02-14 Mozilla representative — Mozilla requested English translations for EV CP/CPS sections, test-site verification, and a hierarchy diagram including EV.
6. 2011-02-18 A-trust representative — A-Trust provided EV-related translations, updated the hierarchy diagram, and said the test website could be verified in Firefox.
7. 2011-03-04 Mozilla representative — Mozilla asked where the OCSP availability and update requirements were documented.
8. 2011-03-08 A-trust representative — A-Trust said the CP was updated so the OCSP response nextUpdate field is not set.
9. 2011-05-26 Mozilla representative — Mozilla summarized the assessment and said it intended to approve the request.
10. 2011-06-02 Mozilla representative — Mozilla approved the request and said it would file NSS and PSM bugs for the changes.