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
This didn't seem to cause issues for certain types of certificates - the certs generated using the Microsoft certGen.sh were able to provision without issue, but upon switching to production certificates, we received the below json:
{"errorCode":401002,"trackingId":"701c9c8f-e467-47d8-8a01-c805a19ab22a","message":"Unauthorized","timestampUtc":"2024-02-08T18:13:04.331944Z"}
I was able to verify the api version impacted the response using curl and I updated the PROV_API_VERSION, rebuilt the sdk, and have our devices provisioning successfully.
The text was updated successfully, but these errors were encountered:
in the current version of the sdk, the prov api version is 2019-03-31
azure-iot-sdk-c/provisioning_client/inc/azure_prov_client/prov_client_const.h
Line 18 in 6b77538
the latest version supported by the dps is 2021-06-01
https://learn.microsoft.com/en-us/rest/api/iot-dps/device/runtime-registration/register-device?view=rest-iot-dps-device-2021-06-01
This didn't seem to cause issues for certain types of certificates - the certs generated using the Microsoft certGen.sh were able to provision without issue, but upon switching to production certificates, we received the below json:
{"errorCode":401002,"trackingId":"701c9c8f-e467-47d8-8a01-c805a19ab22a","message":"Unauthorized","timestampUtc":"2024-02-08T18:13:04.331944Z"}
I was able to verify the api version impacted the response using curl and I updated the PROV_API_VERSION, rebuilt the sdk, and have our devices provisioning successfully.
The text was updated successfully, but these errors were encountered: