medcrypt::guardian::utilities::InitializeFiles

Overview

This is the storage for initialization files used to initialize Guardian.

Requirements:

  • All const char* inputs should be set to the beginning of the loaded buffer.

  • All size_t inputs should be set to the size of the data loaded in the buffer.

Usage example:

Include:

#include <InitializeFiles.h>

Syntax:

struct medcrypt::guardian::utilities::InitializeFiles;

Structure members

Member details

TrustStore variable

  • Description: Root certificate authority TrustStore file buffer for validating certificates.

  • Type: const char*

  • Syntax:

TrustStoreSize variable

  • Description: Size of the TrustStore file buffer.

  • Type: size_t

  • Syntax:

PrivateIdentity variable

  • Description: Device private identity containing cryptographic keys.

  • Type: const char*

  • Security: Must be kept secure and never transmitted.

  • Syntax:

PrivateIdentitySize variable

  • Description: Size of the PrivateIdentity file buffer.

  • Type: size_t

  • Syntax:

CertifiedProfile variable

  • Description: Device certified profile containing certificates and configuration.

  • Type: const char*

  • Syntax:

CertifiedProfileSize variable

  • Description: Size of the CertifiedProfile file buffer.

  • Type: size_t

  • Syntax:

CertifiedCertificateRevocations variable

  • Description: File buffer for Certificate Revocation List (CRL).

  • Type: const char*

  • Syntax:

CertifiedCertificateRevocationsSize variable

  • Description: Size of the CertifiedCertificateRevocations data in bytes.

  • Type: size_t

CertifiedCertificateRevocationsSize variable

  • Description: File buffer size for Certificate Revocation List (CRL).

  • Type: const char*

  • Syntax:

Debugging and logging

Guardian does not create log files. Instead, logging is controlled by the application:

  • Guardian logs to stdout and stderr, which appear in the terminal/CLI of the running application during execution. Look for specific error codes or connection failures in the output.

  • Custom logging: Use SetLoggingCallback to redirect log messages to a callback function, stopping terminal output and allowing custom log handling

  • Log control: Applications can control log level and verbosity.

  • Guardian Cloud UI: Check the Guardian Cloud interface for additional error details and provisioning status.

Last updated