You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 22, 2022. It is now read-only.
When configuring the IoT Hub device client to use a certificate for my IoT Edge Gateway, in transparent mode, passing my certificate to IoTHubDeviceClient_LL_SetOption doesn't work. I had to modify the certs.c file and add my cert directly to the certificates array.
Is this the supported method or am I doing this incorrectly?
If this is is the only way to get this cert in, would it be possible to add another build flag similar to USE_BALTIMORE_CERT for using an IoT Edge cert instead? Maybe something like build.extra_flags=-DESP8266 -DDONT_USE_UPLOADTOBLOB -DUSE_IOT_EDGE_CERT.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When configuring the IoT Hub device client to use a certificate for my IoT Edge Gateway, in transparent mode, passing my certificate to IoTHubDeviceClient_LL_SetOption doesn't work. I had to modify the certs.c file and add my cert directly to the certificates array.
Is this the supported method or am I doing this incorrectly?
If this is is the only way to get this cert in, would it be possible to add another build flag similar to USE_BALTIMORE_CERT for using an IoT Edge cert instead? Maybe something like build.extra_flags=-DESP8266 -DDONT_USE_UPLOADTOBLOB -DUSE_IOT_EDGE_CERT.
The text was updated successfully, but these errors were encountered: