Hi Wayne, In short, this is an optional field that the CCADB does not technically enforce, and there is no policy requirement to populate this information.
The `Public Test Infrastructure URL` field appears in the "PKI Hierarchy" section of the Root Information tab in Add/Update Root Request cases, and this field is written to root certificate records. The intent is simply to collect and centralize publicly accessible test infrastructure information. One source of inspiration for the field is Apply for Inclusion <https://googlechrome.github.io/chromerootprogram/apply-for-inclusion/>, which views operating a publicly accessible test infrastructure that mirrors the production environment as a positive indicator. Would it be helpful if we updated the tooltip to instead say "Optionally provide [...]"? Is there other information in the tooltip that you think would be helpful? Thank you -Chris On Thu, Mar 26, 2026 at 4:08 PM Wayne Thayer <[email protected]> wrote: > Hi Chris, > > I'm looking for information about the new `Public Test Infrastructure URL' > field. The description for the new `Automation Solution Attestation` field > makes it clear that it relates to the Chrome root store policy 1.8 > attestation requirement. However, the `Public Test Infrastructure URL' has > a description that doesn't obviously match the new Chrome policy. The CCADB > description states: > > *Provide a publicly accessible URL to documentation describing the CA > Owner’s test infrastructure. This documentation should describe the test > environment (e.g., available endpoints, features, and profiles), the known > and expected differences between the production infrastructure, and a clear > process for how community members can gain access for interoperability > testing.* > > Can you provide more information on the policy requirements for populating > this field? > > Thanks, > > Wayne > > On Mon, Mar 16, 2026 at 10:07 AM 'Chris Clements' via CCADB Public < > [email protected]> wrote: > >> All, >> >> On March 20, 2026, the CCADB will be updated to support multiple full CRL >> URLs, among other things described in detail below. >> >> The CCADB will be unavailable to CA Owners from March 19, 2026, at >> approximately 08:00PM PT, until March 20, 2026, at approximately 10:00AM PT. >> >> The new functionality should: >> >> - Add a new editable `JSON Array of all Full CRL URLs` field to >> certificate records that allows for a JSON array whose elements are the >> set >> of distinct full CRLDP URLs appearing in time-valid certificates issued by >> the CA. The existing `Full CRL Issued By This CA` field will become read >> only and will automatically convey the first URL presented in the new >> `JSON >> Array of all Full CRL URLs` field. Validation for these CRL related fields >> will enforce proper JSON array formatting. The ‘JSON Array of All Full CRL >> URLs’ field previously included the word ‘expired’ when a certificate was >> expired and ‘revoked’ when a certificate was revoked. However, after this >> release, these terms will no longer be reflected. >> - Update the AddUpdateIntermediateCertAPI to support the new `JSON >> Array of all Full CRL URLs` field and depreciate `Full CRL Issued By This >> CA`. >> - Add new `Automation Solution Attestation` and `Public Test >> Infrastructure URL` fields for root certificate records; these fields can >> be updated via the "Add/Update Root Request" case UI. >> - Add an `Apple Root Program Policy Agreement` field to the Apple tab >> of the “Root Inclusion Request” case UI. >> - Introduce a short time delay when saving certificate record >> information to help avoid creating multiple identical Non-Audit Document >> records. >> - Update the `Subordinate CA Owner` tooltip to align with CCADB >> Policy Version 2.1. >> >> During this update, values from the existing `Full CRL Issued By This CA` >> field will populate the new `JSON Array of all Full CRL URLs` field. CA >> Owners do not need to take action during the update. Once the update is >> complete, CA Owners will be responsible for maintaining the values for the >> `JSON Array of all Full CRL URLs` and `JSON Array of Partitioned CRL URLs`. >> >> We will send a copy of this message to all CA Owners in the CCADB and >> plan to send another message here upon completing the update. >> >> Thank you >> -Chris, on behalf of the CCADB Steering Committee >> >> -- >> You received this message because you are subscribed to the Google Groups >> "CCADB Public" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion visit >> https://groups.google.com/a/ccadb.org/d/msgid/public/CAAbw9mChz9CgMMDjtjNQq-b7D%3DFDk2BNKt_6VFwbXyu4UuOM1A%40mail.gmail.com >> <https://groups.google.com/a/ccadb.org/d/msgid/public/CAAbw9mChz9CgMMDjtjNQq-b7D%3DFDk2BNKt_6VFwbXyu4UuOM1A%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "CCADB Public" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/ccadb.org/d/msgid/public/CAAbw9mBpvWsZ7EvZqnGxtCT8V0UZ50s-i3fWdtmjP7rPhX2tcw%40mail.gmail.com.
