question

ChadMcQuillen-4325 avatar image
1 Vote"
ChadMcQuillen-4325 asked asergaz commented

Is the DPS Registration ID naming restrictions documented inconsistently?

Per this link:

https://docs.microsoft.com/en-us/azure/iot-dps/concepts-service

Under Individual enrollment:

The registration ID in an individual enrollment is alphanumeric, lowercase, and may contain hyphens.

Under Registration ID:

The registration ID is alphanumeric, case insensitive, and may contain special characters including colon, period, underscore and hyphen.

Why is one more restrictive than the other?

azure-iot-dps
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

AshokPeddakotla-MSFT avatar image
1 Vote"
AshokPeddakotla-MSFT answered asergaz commented

@ChadMcQuillen-4325 Great question and thank you for pointing the differences.

We will get the documentation updated accordingly with more clarity. As mentioned, The registration ID in an individual enrollment is alphanumeric, lowercase, and may contain hyphens.

Individual Enrollment:

107046-image.png

Group Enrollment:

106968-image.png

If the above response is helpful, please click "Accept Answer" and upvote it.


image.png (16.6 KiB)
image.png (9.5 KiB)
· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

"As mentioned, The registration ID in an individual enrollment is alphanumeric, lowercase, and may contain hyphens."

What you just stated contradicts what you highlighted in the first image. I can type "FOO" in all uppercase and it will accept it. Same if I uploaded an X.509 certificate with a CN using uppercase. Furthermore, in the "Add Enrollment Group" image where it states "...must only contain lowercase alphanumeric and hyphen" I can also type "FOO" in all uppercase and it will accept it as well. The documentation and help text is clearly out of synch with what has actually been implemented. Please advise.

0 Votes 0 ·

Gotcha. I am checking on this issue with our team and will update the doc with more clarity. Thanks again for the detailed inputs.

0 Votes 0 ·
asergaz avatar image asergaz ChadMcQuillen-4325 ·

Hello @ChadMcQuillen-4325 I want to appreciate all your time so far. Please allow us few more days as we update the doc accordingly. Will let you know as soon as it is done.

Thank you!

0 Votes 0 ·