This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi,
There are multiple SAS and X.509 on the connect screen of the device.
How do you use them properly?
Authentication type - Authentication method:
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(19.2, 71%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED%3C/text%3E%3C/svg%3E)
Hi,
All the options for device authentication with IoT Central are described here: https://learn.microsoft.com/azure/iot-central/core/concepts-device-authentication
Let me know if that article answers your questions.
Regards,
Dominic
Hi @Dom ,
Thank you for reply.
The content is written for "3.Individual enrollment" but not for "1.SAS" and "2.X.509".
Any additional information?
The content covers all three options:
Regards, Dominic
Hi,
I am a little confused.
Hi,
On the Enrollment Groups screens you can define device enrollment groups that use either SAS or X.509.
When you go to a specific device and select either Shared Access Signature (SAS) or Certificates (X.509), you can chose either a key derived from your default SAS enrollment groups, or an X.509 cert derived from the root key in your X.509 enrollment group. The devices page just shows default values you can use. A device could use a SAS key derived from any of your SAS enrollment groups or a cert from any of your X.509 enrollment groups.
If you choose Individual enrollment - the keys or certs the device uses are not derived from the root keys or certs defined on the Enrollment group pages - you'll need to add either root keys or upload the certs on the devices page.
Regards,
Dominic
Hi @Dom ,
Thank you for your detailed explanation.