Corrected the comments about the treatment of device certs when using TrustCUSTOM v/s other variants - added code that will plug in the provided custom device cert to the network context. No code needed for other variants - esp-tls handles device cert attachment internally

Author: sckulkarni246

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

@@ -94,12 +94,20 @@ TlsTransportStatus_t TLS_Socket_Connect( NetworkContext_t * pNetworkContext,
 
     esp_transport_ssl_use_secure_element( pNetworkContext->xTransport );
 
-    #ifndef CONFIG_ATECC608A_TNG
-        /* This is either a TrustFLEX or a TrustCUSTOM chip - generate (using atcacert_* API) or plug in 
-            your certificate here (if the CSR was generated using ATECC608 and cert is available as a .der)
+    #ifdef CONFIG_ATECC608A_TCUSTOM
+        /*  This is TrustCUSTOM chip - the private key will be used from the ATECC608 device slot 0.
+            We will plug in your custom device certificate here (should be in DER format).
         */
+        if ( pNetworkCredentials->pucClientCert )
+        {
+            esp_transport_ssl_set_client_cert_data_der( pNetworkContext->xTransport, ( const char *) pNetworkCredentials->pucClientCert, pNetworkCredentials->xClientCertSize );
+        }
+
+       
     #else
-        /* No action needed - cryptoauthlib will generate and attach the cert to the network context */
+        /*  This is either the Trust&GO or the TrustFLEX chip - the private key will be used from ATECC608 device slot 0.
+            We don't need to add certs to the network context as the esp-tls does that for us using cryptoauthlib API.
+        */
 
     #endif