Facing a problem with registering device via azure dps. I've tested dps with few different devices with ARM processors, used same certificate for them and worked fine. However, when i use this certificate with device with MIPS processor, i get authorization error. I've followed all the tutorials for CA creation and etc, can't find any solution.
There might be a problem with the location of certification on the device. Ensure that on the device you have access to the certification and the client uses the right one. You might need additional configuration to ensure that you provide the certification to the MIPS devices in the right way.
The first thing that you should do is to add extra logs on the device and check if you are using the right device certification when you connect to Azure IoT services.
Hi, i couldn't trace the problem. I will try to provide more details: i use x509 certificate(leaf) for individual enrollment, which i tested for various devices with mips and arm architecture with same procedure, for each arm device it works fine. For every mips, it does not. Authorization error is logged as it tries to register the device. Both architecture devices have same versions libraries and etc.. No different ssl algorithms or whatever. Is there a difference for certificate options for different architectures or something, or some additional functions from library to be used for mips architecture? Can this be somehow involved with encoding/decoding functions in the library as different architectures might behave differently? Everything is in C language.
Edit: can this impact if mips are big endian and arm is little endian?
Btw, certificates was created on windows, with azure SDK followed by provided tutorials
3 people are following this question.
