Skip to content

Commit 31b21c4

Browse files
committed
Added a comment about the treatment of client cert when not using an ATECC608-Trust&GO device
1 parent 43a6073 commit 31b21c4

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

demos/projects/ESPRESSIF/esp32/components/sample-azure-iot/transport_tls_esp32.c

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -94,6 +94,15 @@ TlsTransportStatus_t TLS_Socket_Connect( NetworkContext_t * pNetworkContext,
9494

9595
esp_transport_ssl_use_secure_element( pNetworkContext->xTransport );
9696

97+
#ifndef CONFIG_ATECC608A_TNG
98+
/* This is either a TrustFLEX or a TrustCUSTOM chip - generate (using atcacert_* API) or plug in
99+
your certificate here (if the CSR was generated using ATECC608 and cert is available as a .der)
100+
*/
101+
#else
102+
/* No action needed - cryptoauthlib will generate and attach the cert to the network context */
103+
104+
#endif
105+
97106
#else
98107

99108
if ( pNetworkCredentials->pucClientCert )

0 commit comments

Comments
 (0)