Currently, with SPDM attestation, there is no way to uniquely identify an Attester. An attestation is done for all Attesters in a managed host. If the attestation fails for a specific Attester, or if a given Attester cannot be run in a particular state, there needs to be a way to run attestation individually. For this purpose, a structure/enum need to be envisaged which would allow to uniquely identify an Attester in a DC. That structure/enum should be serializable/deserializable into/from a string.
The first field of that structure will be an enumeration, indicating the device type. The other fields can be variable, e.g. they can also be an enumeration, describing each device.
There is an existing gRPC command to invoke an attestation for a given machine id, this needs to be updated to also accept a specific Attester, but the machine-based attestation should be retained.
Currently, with SPDM attestation, there is no way to uniquely identify an Attester. An attestation is done for all Attesters in a managed host. If the attestation fails for a specific Attester, or if a given Attester cannot be run in a particular state, there needs to be a way to run attestation individually. For this purpose, a structure/enum need to be envisaged which would allow to uniquely identify an Attester in a DC. That structure/enum should be serializable/deserializable into/from a string.
The first field of that structure will be an enumeration, indicating the device type. The other fields can be variable, e.g. they can also be an enumeration, describing each device.
There is an existing gRPC command to invoke an attestation for a given machine id, this needs to be updated to also accept a specific Attester, but the machine-based attestation should be retained.