CA/CCADB Dashboard: Difference between revisions
(added instructions for filing these bugs) |
m (cleaned up the ordering) |
||
| Line 19: | Line 19: | ||
"status_whiteboard":"ccadb-api", | "status_whiteboard":"ccadb-api", | ||
"include_fields": "whiteboard, id, summary, last_change_time", | "include_fields": "whiteboard, id, summary, last_change_time", | ||
"order": " | "order": "id" | ||
} | } | ||
</bugzilla> | </bugzilla> | ||
| Line 41: | Line 41: | ||
"whiteboard":"ccadb-bug", | "whiteboard":"ccadb-bug", | ||
"include_fields": "priority, id, summary, last_change_time", | "include_fields": "priority, id, summary, last_change_time", | ||
"order": "priority ASC | "order": "priority ASC" | ||
} | } | ||
</bugzilla> | </bugzilla> | ||
| Line 64: | Line 64: | ||
"v2": "ccadb", | "v2": "ccadb", | ||
"include_fields": "priority, id, summary,last_change_time", | "include_fields": "priority, id, summary,last_change_time", | ||
"order": "priority ASC | "order": "priority ASC" | ||
} | } | ||
</bugzilla> | </bugzilla> | ||
Revision as of 23:36, 3 May 2023
Dashboard for Common CA Database Updates
CCADB API Access
Requests for API access to the CCADB as per https://github.com/mozilla/CCADB-Tools/tree/master/API_AddUpdateIntermediateCert
To file a CCADB API Access Request, use:
Product: CA Program
Component: Common CA Database
Whiteboard: [ccadb-api]
| Whiteboard | ID | Summary | Last change time |
|---|---|---|---|
| [ccadb-api] in sandbox | 1770056 | Google Trust Services - Request for access to CCADB API | 2022-11-14T22:22:21Z |
| [ccadb-api] in sandbox | 1779692 | NAVER Cloud - Request for access to CCADB API | 2023-01-12T18:25:21Z |
| [ccadb-api] in sandbox | 1793511 | Microsoft - Request for access to CCADB API | 2023-09-18T16:26:31Z |
| [ccadb-api] | 1798894 | Chrome Root Program - Provide OAuth and API for Chrome to automate root store updates to the CCADB | 2025-01-07T16:02:32Z |
| [ccadb-api] | 1901864 | Certainly: Request for access to CCADB API | 2025-04-01T15:51:05Z |
| [ccadb-api] | 1916851 | Amazon Trust Services - Request for Access to CCADB API | 2024-09-13T16:08:07Z |
6 Total; 6 Open (100%); 0 Resolved (0%); 0 Verified (0%);
Bugs
Bugs that unintentionally remove pre-existing functionality or negatively impact CCADB users should have priority over Enhancements, and should be set to P1. Low impact bugs will start at P4 and be considered with ERs. If it's a low LOE bug (less than 4 hours of work) it can go from P4 to P1 without prioritization/design.
To file a CCADB Bug, use:
Product: CA Program
Component: Common CA Database
Whiteboard: [ccadb-bug]
| Priority | ID | Summary | Last change time |
|---|---|---|---|
| P3 | 1747829 | Disable the pull-down (Edit and Change Owner) in all tab views for CAs and Root Store Operators | 2025-01-08T16:35:52Z |
1 Total; 1 Open (100%); 0 Resolved (0%); 0 Verified (0%);
Enhancement Requests
The Priority values are used as follows:
- P1 - Development in progress
- P2 - Design complete
- P3 - Prioritized
- P4 or not set - To be prioritized and scheduled later
Important: Do not enter a value into the Whiteboard field to file a CCADB Enhancement Request.
70 Total; 70 Open (100%); 0 Resolved (0%); 0 Verified (0%);
Closed
A historical view of past CCADB updates (from May 2021 onward) may be found here: