CCADB Update: Enhancements to the CA/B Forum Certificate Policy Identifier and Intended Use Case(s) Served fields

139 views
Skip to first unread message

CCADB Support

unread,
Jul 28, 2026, 11:03:51 AMJul 28
to CCADB Support, public
All,

On July 30, 2026 at approximately 08:00 PM PT, the CCADB will be updated with enhancements to the `CA/B Forum Certificate Policy Identifier` and `Intended Use Case(s) Served` fields.

This release includes:
  • Updating the `Intended Use Case(s) Served` available options in the Add/Update Root Request case by adding BIMI and removing a few existing use cases (i.e., Encrypting File System, IP Security, and Document Signing AATL) from future field selection. This field also includes validation logic that aligns with the single-use hierarchies described in multiple CCADB Root Store Operator policies.
  • Adding other `CA/B Forum Certificate Policy Identifiers` to the available selections for completeness. This change applies to the Add/Update Root Request case and directly to intermediate certificate records.
We will send another message when the update is complete.

Best regards,
-CCADB Support

CCADB Support

unread,
Jul 31, 2026, 1:40:35 PMJul 31
to CCADB Support, public

Hi All,


On July 30, 2026, the CCADB was updated with enhancements to the `CA/B Forum Certificate Policy Identifier` and `Intended Use Case(s) Served` fields.


This update:

  • Changed the `Intended Use Case(s) Served` available options in the Add/Update Root Request case by adding BIMI and removing a few existing use cases (i.e., Encrypting File System, IP Security, and Document Signing AATL) from field selection. This field also includes validation logic that aligns with the single-use hierarchies described in multiple CCADB Root Store Operator policies.

  • Added other `CA/B Forum Certificate Policy Identifiers` to the available selections for completeness. This change applies to the Add/Update Root Request case and directly to intermediate certificate records.


The ROOT INFORMATION user guide has been updated with these changes. 


Please continue to contact sup...@ccadb.org with any questions or issues. 



Thank you

- CCADB Support

Reply all
Reply to author
Forward
0 new messages