← Google Trust Services LLC cases
Bugzilla #1770056 CA Inclusion Request

Google Trust Services - Request for access to CCADB API

ASSIGNED Google Trust Services LLC
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 Google Trust Services requesting access to the CCADB API. The reporter stated that Google Trust Services previously requested and was granted access to the CCADB API in the Sandbox environment. A follow-up was sent to ask for the status. In a later update, Google Trust Services said the project was put on hold and that they looked into resuming it. They reported that the callback/host URL they had was https://sbxccadb-ccadb.cs37.force.com, but that this page returns a TLS error because the certificate is not valid for it (they said it is valid for *.cs279.force.com). They also reported that using the cs279.force.com parent domain when querying the OAuth authorize endpoint resulted in an error: error=invalid_client_id. They requested confirmation that their authentication information is correct before troubleshooting further, noting that the information they have may be outdated.

Model: gpt-5.4-nano Generated: 2026-06-13 21:29 UTC Revised: 2026-06-16 18:43 UTC Confidence: 0.50 3 comments
Chronology
  1. Google Trust Services reported that it had been granted CCADB API access in the Sandbox environment.
  2. A follow-up was sent to check the status of the CCADB API access request.
  3. Google Trust Services reported the project was on hold and that resuming it encountered TLS and OAuth client ID errors, requesting verification of authentication information.
Thread Activity
  1. Mozilla representative — Reported that Google Trust Services previously requested and has been granted access to the CCADB API in Sandbox.
  2. Apicalapps representative — Sent a follow-up email to find the status.
  3. Google representative — Said the project was put on hold, that resuming it found outdated callback/host information causing a TLS error, and that using the cs279.force.com domain produced invalid_client_id; requested confirmation that authentication information is correct before further troubleshooting.
Participants
Mozilla representative Apicalapps representative Google representative
External References
Similar Local Cases
#1770052 RESOLVED CA Inclusion Request Opened 2022-05-18 · Closed 2024-01-19 · 42% similar
SSL.com - Request for access to CCADB API

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

Confirm action