The connection string has an invalid value for property: DeviceId

Alexandre Alison 36

Hello,

In our software, we use an already defined device named "IoTDeviceCheck" (deviceId) to setup the connection with our IOT hub.

It is possible to create a DeviceClient with such deviceId with most culture info (en-us, de-ch,..) but not with "tr-TR" : it throws an exception "The connection string has an invalid value for property: DeviceId". Because in IotHubConnectionStringBuilder:ValidateFormat, regex.IsMatch(value) returns false.

The regex (IdNameRegex) for idName is "^[A-Za-z0-9-:.+%_#*?!(),=@;$']{1,128}$" with regexOptions = RegexOptions.Compiled | RegexOptions.IgnoreCase;

In Turkhish, this fails because the "i" character does not seem to match the a-z part of the regular expression (and because the RegexOptions.CultureInvariant is not used).

We now perform the setup of the communication using in a CultureInfo.InvariantCulture task and it solves the problem.

So this means that HostName, IdName and SharedAccessKeyName are culture dependent.

We had this issue only on setup but our application can be used by customers from many countries (so a device id could be created on a culture and then used in another one) so that could be a common limitation.

Could somebody confirm that HostName, IdName and SharedAccessKeyName are meant to be culture dependent? (I was not able to find any documentation about this).

(SharedAccessKeyRegex, SharedAccessSignatureRegex and X509CertRegex are also using the same regexOptions).

Thanks

Alex

QuantumCache 20,346 Reputation points

2020-11-02T23:25:36.56+00:00

Hello @Alexandre Alison , Thanks for reaching out to us!
We are looking into this.
QuantumCache 20,346 Reputation points

2020-11-03T01:00:36.743+00:00

Hello @Alexandre Alison , Could you please provide a few examples of working and non-working device-Ids. As far as I know, the device-ID is case sensitive.
Alexandre Alison 36 Reputation points

2020-11-03T07:30:23.93+00:00

Hello,

Case sensitive? do you mean Culture dependent? ( regexOptions = RegexOptions.Compiled | RegexOptions.IgnoreCase).

To validate my hypothesis, I quickly did a unit test (please see attached file 37079-regextest.txt).

so deviceId = "IoTDeviceCheck" is nok and "oTDevceCheck" is ok.

Thanks

Alex
QuantumCache 20,346 Reputation points

2020-11-03T23:37:36.93+00:00

We are checking on this ... please stay tuned.
QuantumCache 20,346 Reputation points

2020-11-10T17:31:21.607+00:00

Hello @Alexandre Alison , Thanks for the waiting on this issue, I am checking internally with my team on this issue. Please stay tuned and sorry for the delay on this issue. We are trying our best to get the resolution soon.
QuantumCache 20,346 Reputation points

2020-11-13T18:01:17.187+00:00

Hello @Alexandre Alison , I hope your are doing great, sorry for the delay in resolution, we are working with our team on this.

Please stay tuned for further updates. Please add any further queries if you have, to this thread.

Thank you,
Satish.
QuantumCache 20,346 Reputation points

2020-12-07T18:47:16.4+00:00

Hello @Alexandre Alison , Just a checkpoint, We are still working with our team internally.
QuantumCache 20,346 Reputation points

2020-12-07T19:00:06.923+00:00

Hello @Alexandre Alison , Please confirm on the below ask from the product team,

Is it only the “i” or other characters as well?
It looks like the Turkish “i” fails because it’s not an ASCII character (The dotted and dotless “I” are separate letters in Turkish).

(checked against this)
Alexandre Alison 36 Reputation points

2020-12-09T09:58:55.927+00:00

Hello @QuantumCache ,

I cannot confirm you that because I do not speak Turkish.

I had a problem regarding the 'i' (latin i) with CultureInfo.tr-Tr: the IdNameRegex returns false and the deviceId is considered as invalid. This means that deviceId is culture dependent.

This device ("IotDeviceCheck") was created (probably with CultureInfo.en-us) for testing purposes.

The unit test tries to connect to it using different CultureInfo. But because of this IdNameRegex, it failed with CultureInfo.tr-Tr.

It tests a small subset of CultureInfo and it might fail for other non-latin language too.

That's why I asked for a confirmation: are HostName, IdName and SharedAccessKeyName, SharedAccessKeyRegex, SharedAccessSignatureRegex and X509CertRegex supposed to be culture dependent?

Best

Alex
QuantumCache 20,346 Reputation points

2020-12-09T16:02:42.187+00:00

Hello @Alexandre Alison , Thanks for the information, let me check with my team on this.
QuantumCache 20,346 Reputation points

2020-12-16T03:24:16.663+00:00

Hello @Alexandre Alison , below is the PR submitted with respect to this issue.

Use CultureInvariant for validating device connection string values
Alexandre Alison 36 Reputation points

2020-12-16T13:40:56.277+00:00

Hello @QuantumCache ,

Thanks you for the PR.

Best Regards

Alex
QuantumCache 20,346 Reputation points

2020-12-18T19:38:55.223+00:00

Hello @Alexandre Alison , We have our product team looking into this issue. Below is the latest comment from our product team, but we will keep you posted for further updates.

the regex match in SDK’s need to be culture invariant .
QuantumCache 20,346 Reputation points

2021-01-04T22:47:47.797+00:00

Hello @Alexandre Alison , Just checking back, could you please let us know if you need further help in this matter. Please see the below responses and let us know if the latest fix helped to unblock your issue.
Alexandre Alison 36 Reputation points

2021-01-08T14:12:01.093+00:00

Hello @António Sérgio Azevedo and @QuantumCache ,

Sorry for my late answer, I came back from holidays this week.

I can wait for the new SDK to test it or test it using a private SDK drop.

Best
QuantumCache 20,346 Reputation points

2021-01-08T15:12:48.367+00:00

Hello @Alexandre Alison Thanks for the response.

Please let us know once you have tested the publicly available SDK.
QuantumCache 20,346 Reputation points

2021-01-11T23:23:01.197+00:00

Hello @Alexandre Alison ,Just checking in if you have had a chance to see the previous response.
Please enable your preferred alert types on your Profile's Settings to get instant notifications on this thread's discussions. Here is how to subscribe to a notification.

Accepted answer

António Sérgio Azevedo 7,671 Reputation points Microsoft Employee

2020-12-28T16:53:01.48+00:00
Hello @Alexandre Alison ,
Thank you so much for your time. I have confirmed that the PR should fix the issue reported: https://github.com/Azure/azure-iot-sdk-csharp/pull/1716

Please confirm on your side by building the source code and testing;

Or you can wait for the next SDK release planed to the first week of January;

Alternatively we can provide you with a private SDK drop as well.

We would love to hear from you once you try out the fix and if solved, please mark this as the answer to help others finding the best content easily :)!
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

The connection string has an invalid value for property: DeviceId

0 additional answers

Your answer