Make sure that Git is added to the environment variables accessible to the command window. If you don't have a hub yet, you can follow the steps in Create an IoT hub. If you don't have an Azure subscription, create a free account before you begin.Īn IoT hub in your Azure subscription.
For more information, see Managing test CA certificates for samples and tutorials in the GitHub repository for the Azure IoT Hub Device SDK for C. You must use your own best practices for certificate creation and lifetime management in a production environment. The certificates contain hard-coded passwords (“1234”) and expire after 30 days. Certificates created by them must not be used for production. The scripts are provided for demonstration purposes only. The scripts are included with the Azure IoT Hub Device SDK for C.
#Openssl ca how to#
Microsoft provides PowerShell and Bash scripts to help you understand how to create your own X.509 certificates and authenticate them to an IoT hub. A self-managed private CA with at least one subordinate CA chained to your internal root CA, with client certificates for your devices that are signed by your subordinate CAs, allows you to simulate a recommended production environment.
However, creating your own self-managed, private CA that uses an internal root CA as the trust anchor is adequate for testing environments. For more information about getting an X.509 CA certificate from a professional certificate services vendor, see the Get an X.509 CA certificate section of Authenticate devices using X.509 CA certificates. You can then issue certificates within your organization from an internal, self-managed certificate authority (CA) chained to the purchased CA certificate as part of a comprehensive public key infrastructure (PKI) strategy. For production environments, we recommend that you purchase an X.509 CA certificate from a professional certificate services vendor. You can use X.509 certificates to authenticate devices to your IoT hub.
0 kommentar(er)
