Creating Keys for CoAP Broker

Our setup includes the use of Product Attestation Authorities (PAAs) to ensure compliance with the Matter protocol.

Key Types and Usages

1. Device Attestation Certificates (DACs)

• Purpose: DACs are used to authenticate devices within the network. They ensure that a device is genuine and authorized to communicate with the broker.
• Usage in Setup: In our setup, DACs are created for each device using the create_dac_and_register.sh script. This script generates a private key and a certificate for the device, which is then registered with the backend (stored in a postgres database).

2. Product Attestation Authorities (PAAs)

• Purpose: PAAs are higher-level certificates that validate the authenticity of DACs. They act as a root of trust in the certificate hierarchy.
• Usage in Setup: The create_paa.sh script generates a PAA certificate and key, which are used to sign DACs. This ensures that all device certificates are traceable back to a trusted authority.

Matter Compliance

• Implementation: Our use of PAAs and DACs ensures that devices can be securely authenticated and communicate within a Matter-compliant ecosystem.

Scripts

For more detailed instructions on creating and managing keys, refer to the respective scripts and their documentation.

scripts/create_paa.sh scripts/create_dac_and_register.sh

These will be replaced when we partner with an official PAA.