Overview
The manifest file format is designed to convey the unique information about a group of secure sub-systems, including unique ID (e.g., serial number), public keys and certificates. This was primarily developed for CryptoAuthentication™ (currently ATECC608, ECC204 and ECC206) and CryptoAutomotive™ (currently TA010, TA100 and TA101) secure sub-system devices. However, it is structured to work for other secure sub-systems as well.
Manifest files provide a way to link an actual Microchip Trust secure sub-system device to the infrastructure environment that it needs to connect to. They are an essential component of the Microchip Trust&GO, TrustMANAGER, TrustFLEX and, optionally, TrustCUSTOM development environments. Whether the device connects to an IoT cloud, a Wireless Power Consortium (WPC) Qi® charger, a LoRaWAN® network or another type of infrastructure, the manifest file uniquely associates each secure sub-system device with its designated environment.
When using Microchip Trust&GO, TrustMANAGER, TrustFLEX or TrustCUSTOM products, a manifest file is generated for a group of secure sub-system devices that are provisioned through the Microchip Just-In-Time provisioning services. Each object entry in the manifest file is known as a signed secure sub-system device, authenticated using a Microchip Elliptic Curve Cryptography (ECC) private key. The manifest file comprises multiple signed secure sub-system device entries, each containing manufacturer details, product information and device-specific data.
The manifest file is securely provided only to the customer who orders the group of secure sub-system devices. Access to these files is integrated into the development and provisioning workflow offered by Microchip. Once provisioning is complete, the manifest file is made available for download.