Store certificates and certificate details (step 5) certificate details are optional

kreinhar commented 2 years ago

[ ] use the url provide by Reuben 'GET /tenant/tenants/{tenantID}/trusted-certificates'
[ ] depack pkcs 7 to get all x509 details .Possibly add an openssl library so that it is feasable with https://www.baeldung.com/linux/openssl-extract-certificate-info#extracting-specific-information-from-the-certificate
[ ] set "status": "DISABLED", and "autoRegistrationEnabled": "false",
[ ]

kreinhar commented 2 years ago

store all necessary information

kreinhar commented 2 years ago

it seams https://cumulocity.com/guides/device-sdk/mqtt/#upload-your-ca-certificate we will not have as response a unique identifier. So we will not have so far a relation from the certificate to the device.

but

the certificate contains a 'Serial Number - Unique serial number that is created for each certificate that is created by an issuer,'

as we have to read anyhow all informations out of the certificate ( https://cumulocity.com/guides/device-sdk/mqtt/#introduction-to-x509-certificates) we could possibly use theserial number as "external-ID" of the device. I couldn't verify this so far if this is possible but it would bring us a "kind of" relation

Cumulocity-IoT / cumulocity-pki-integration