Quickstart: Provision an X.509 certificate simulated device

The following prerequisites are for a Windows development environment. For Linux or macOS, see the appropriate section in Prepare your development environment in the SDK documentation.

• Install Visual Studio 2022 with the 'Desktop development with C++' workload enabled. Visual Studio 2015, Visual Studio 2017, and Visual Studio 19 are also supported. For Linux or macOS, see the appropriate section in Prepare your development environment in the SDK documentation.

• Install the latest CMake build system. Make sure you check the option that adds the CMake executable to your path.

  Important

  Confirm that the Visual Studio prerequisites (Visual Studio and the 'Desktop development with C++' workload) are installed on your machine, before starting the CMake installation. Once the prerequisites are in place, and the download is verified, install the CMake build system. Also, be aware that older versions of the CMake build system fail to generate the solution file used in this article. Make sure to use the latest version of CMake.

The following prerequisites are for a Windows development environment. For Linux or macOS, see the appropriate section in Prepare your development environment in the SDK documentation.

• Install .NET SDK 6.0 or later on your Windows-based machine. You can use the following command to check your version.

  dotnet --info
  

The following prerequisites are for a Windows development environment. For Linux or macOS, see the appropriate section in Prepare your development environment in the SDK documentation.

• Install Node.js v4.0 or above on your machine.

The following prerequisites are for a Windows development environment.

• Python 3.6 or later on your machine.

The following prerequisites are for a Windows development environment. For Linux or macOS, see the appropriate section in Prepare your development environment in the SDK documentation.

• Install the Java SE Development Kit 8 or later on your machine.

• Download and install Maven.

In this section, you prepare a development environment that's used to build the Azure IoT C SDK. The sample code attempts to provision the device, during the device's boot sequence.

1. Open a web browser, and go to the Release page of the Azure IoT C SDK.

2. Select the Tags tab at the top of the page.

3. Copy the tag name for the latest release of the Azure IoT C SDK.

4. In your Windows command prompt, run the following commands to clone the latest release of the Azure IoT Device SDK for C GitHub repository. Replace <release-tag> with the tag you copied in the previous step, for example: lts_01_2023.

   git clone -b <release-tag> https://github.com/Azure/azure-iot-sdk-c.git
   cd azure-iot-sdk-c
   git submodule update --init
   

   This operation could take several minutes to complete.

5. When the operation is complete, run the following commands from the azure-iot-sdk-c directory:

   mkdir cmake
   cd cmake
   

6. The code sample uses an X.509 certificate to provide attestation via X.509 authentication. Run the following command to build a version of the SDK specific to your development platform that includes the device provisioning client. A Visual Studio solution for the simulated device is generated in the cmake directory.

   When specifying the path used with -Dhsm_custom_lib in the following command, make sure to use the absolute path to the library in the cmake directory you previously created. The path shown assumes that you cloned the C SDK in the root directory of the C drive. If you used another directory, adjust the path accordingly.

   • Windows
   • Linux

   cmake -Duse_prov_client:BOOL=ON -Dhsm_custom_lib=c:/azure-iot-sdk-c/cmake/provisioning_client/samples/custom_hsm_example/Debug/custom_hsm_example.lib ..
   

7. When the build succeeds, the last few output lines look similar to the following output:

   -- Building for: Visual Studio 17 2022
   -- Selecting Windows SDK version 10.0.19041.0 to target Windows 10.0.22000.
   -- The C compiler identification is MSVC 19.32.31329.0
   -- The CXX compiler identification is MSVC 19.32.31329.0
   
   ...
   
   -- Configuring done
   -- Generating done
   -- Build files have been written to: C:/azure-iot-sdk-c/cmake
   

In your Windows command prompt, clone the Azure IoT SDK for C# GitHub repository using the following command:

git clone https://github.com/Azure/azure-iot-sdk-csharp.git

In your Windows command prompt, clone the Azure IoT SDK for Node.js GitHub repository using the following command:

git clone https://github.com/Azure/azure-iot-sdk-node.git

In your Windows command prompt, clone the Azure IoT Device SDK for Python GitHub repository using the following command:

git clone -b v2 https://github.com/Azure/azure-iot-sdk-python.git --recursive

1. In your Windows command prompt, clone the Azure IoT Samples for Java GitHub repository using the following command:

   git clone https://github.com/Azure/azure-iot-sdk-java.git --recursive
   

2. Go to the root azure-iot-sdk-java directory and build the project to download all needed packages.

   cd azure-iot-sdk-java
   mvn install -DskipTests=true
   

6. The sample code requires a private key that isn't encrypted. Run the following command to create an unencrypted private key:

   • Windows
   • Linux

   winpty openssl rsa -in device-key.pem -out unencrypted-device-key.pem
   

7. When asked to Enter pass phrase for device-key.pem:, use the same pass phrase you did previously, 1234.

Keep the Git Bash prompt open. You need it later in this quickstart.

The C# sample code is set up to use X.509 certificates that are stored in a password-protected PKCS#12 formatted file (certificate.pfx). You still need the PEM formatted public key certificate file (device-cert.pem) that you just created to create an individual enrollment entry later in this quickstart.

1. To generate the PKCS12 formatted file expected by the sample, enter the following command:

   • Windows
   • Linux

   winpty openssl pkcs12 -inkey device-key.pem -in device-cert.pem -export -out certificate.pfx
   

2. When asked to Enter pass phrase for device-key.pem:, use the same pass phrase you did previously, 1234.

3. When asked to Enter Export Password:, use the password 1234.

4. When asked Verifying - Enter Export Password:, use the password 1234 again.

   A PKCS12 formatted certificate file (certificate.pfx) should now be generated in the directory where you ran the openssl command.

5. Copy the PKCS12 formatted certificate file to the project directory for the X.509 device provisioning sample. The path given is relative to the location where you downloaded the sample repo.

   cp certificate.pfx ./azure-iot-sdk-csharp/provisioning/device/samples/"Getting Started"/X509Sample
   

You don't need the Git Bash prompt for the rest of this quickstart. However, you may want to keep it open to check your certificate if you have problems in later steps.

6. The sample code requires a private key that isn't encrypted. Run the following command to create an unencrypted private key:

   • Windows
   • Linux

   winpty openssl rsa -in device-key.pem -out unencrypted-device-key.pem
   

7. When asked to Enter pass phrase for device-key.pem:, use the same pass phrase you did previously, 1234.

8. Copy the device certificate and unencrypted private key to the project directory for the X.509 device provisioning sample. The path given is relative to the location where you downloaded the SDK.

   cp device-cert.pem ./azure-iot-sdk-node/provisioning/device/samples
   cp unencrypted-device-key.pem ./azure-iot-sdk-node/provisioning/device/samples
   

You don't need the Git Bash prompt for the rest of this quickstart. However, you may want to keep it open to check your certificate if you have problems in later steps.

6. Copy the device certificate and private key to the project directory for the X.509 device provisioning sample. The path given is relative to the location where you downloaded the SDK.

   cp device-cert.pem ./azure-iot-sdk-python/samples/async-hub-scenarios
   cp device-key.pem ./azure-iot-sdk-python/samples/async-hub-scenarios
   

You don't need the Git Bash prompt for the rest of this quickstart. However, you may want to keep it open to check your certificate if you have problems in later steps.

6. The Java sample code requires a private key that isn't encrypted. Run the following command to create an unencrypted private key:

   • Windows
   • Linux

   winpty openssl pkey -in device-key.pem -out unencrypted-device-key.pem
   

7. When asked to Enter pass phrase for device-key.pem:, use the same pass phrase you did previously, 1234.

Keep the Git Bash prompt open. You need it later in this quickstart.

In this section, you use your Git Bash prompt and the Visual Studio IDE.

Configure the provisioning device code

In this section, you update the sample code with your Device Provisioning Service instance information.

1. In the Azure portal, select the Overview tab for your Device Provisioning Service.

2. Copy the ID Scope value.

   

3. Launch Visual Studio and open the new solution file that was created in the cmake directory you created in the root of the azure-iot-sdk-c git repository. The solution file is named azure_iot_sdks.sln.

4. In Solution Explorer for Visual Studio, navigate to Provision_Samples > prov_dev_client_sample > Source Files and open prov_dev_client_sample.c.

5. Find the id_scope constant, and replace the value with your ID Scope value that you copied in step 2.

   static const char* id_scope = "0ne00000A0A";
   

6. Find the definition for the main() function in the same file. Make sure the hsm_type variable is set to SECURE_DEVICE_TYPE_X509.

   SECURE_DEVICE_TYPE hsm_type;
   //hsm_type = SECURE_DEVICE_TYPE_TPM;
   hsm_type = SECURE_DEVICE_TYPE_X509;
   //hsm_type = SECURE_DEVICE_TYPE_SYMMETRIC_KEY;
   

7. Save your changes.

8. Right-click the prov_dev_client_sample project and select Set as Startup Project.

Run the sample

1. On the Visual Studio menu, select Debug > Start without debugging to run the solution. If you're prompted to rebuild the project, select Yes to rebuild the project before running.

   The following output is an example of the simulated device my-x509-device successfully booting up, and connecting to the provisioning service. The device is assigned to an IoT hub and registered:

   Provisioning API Version: 1.8.0
   
   Registering Device
   
   Provisioning Status: PROV_DEVICE_REG_STATUS_CONNECTED
   Provisioning Status: PROV_DEVICE_REG_STATUS_ASSIGNING
   
   Registration Information received from service: contoso-iot-hub-2.azure-devices.cn, deviceId: my-x509-device
   Press enter key to exit:
   

In this section, you use your Windows command prompt.

1. In the Azure portal, select the Overview tab for your Device Provisioning Service.

2. Copy the ID Scope value.

   

3. In your Windows command prompt, change to the X509Sample directory. This directory is located in the .\azure-iot-sdk-csharp\provisioning\device\samples\getting started\X509Sample directory off the directory where you cloned the samples on your computer.

4. Enter the following command to build and run the X.509 device provisioning sample (replace the <IDScope> value with the ID Scope that you copied in the previous section. The certificate file defaults to ./certificate.pfx and prompts for the .pfx password.

   dotnet run -- -s <IDScope>
   

   If you want to pass the certificate and password as a parameter, you can use the following format.

   Note

   Additional parameters can be passed along while running the application to change the TransportType (-t) and the GlobalDeviceEndpoint (-g).

   dotnet run -- -s 0ne00000A0A -c certificate.pfx -p 1234
   

5. The device connects to DPS and is assigned to an IoT hub. Then, the device sends a telemetry message to the IoT hub.

   Loading the certificate...
   Enter the PFX password for certificate.pfx:
   ****
   Found certificate: A33DB11B8883DEE5B1690ACFEAAB69E8E928080B CN=my-x509-device; PrivateKey: True
   Using certificate A33DB11B8883DEE5B1690ACFEAAB69E8E928080B CN=my-x509-device
   Initializing the device provisioning client...
   Initialized for registration Id my-x509-device.
   Registering with the device provisioning service...
   Registration status: Assigned.
   Device my-x509-device registered to MyExampleHub.azure-devices.cn.
   Creating X509 authentication for IoT Hub...
   Testing the provisioned device with IoT Hub...
   Sending a telemetry message...
   Finished.
   

In this section, you use your Windows command prompt.

1. In the Azure portal, select the Overview tab for your Device Provisioning Service.

2. Copy the ID Scope value.

   

3. In your Windows command prompt, go to the sample directory, and install the packages needed by the sample. The path shown is relative to the location where you cloned the SDK.

   cd .\azure-iot-sdk-node\provisioning\device\samples
   npm install
   

   The sample uses five environment variables to authenticate and provision an IoT device using DPS. These environment variables are:

   Variable name	Description
   PROVISIONING_HOST	The endpoint to use for connecting to your DPS instance. For this quickstart, use the global endpoint, global.azure-devices-provisioning.net.
   PROVISIONING_IDSCOPE	The ID Scope for your DPS instance.
   PROVISIONING_REGISTRATION_ID	The registration ID for your device. It must match the subject common name in the device certificate.
   CERTIFICATE_FILE	The path to your device certificate file.
   KEY_FILE	The path to your device private key file.

4. Add environment variables for the global device endpoint and ID scope. Replace <id-scope> with the value you copied in step 2.

   set PROVISIONING_HOST=global.azure-devices-provisioning.net
   set PROVISIONING_IDSCOPE=<id-scope>
   

5. Set the environment variable for the device registration ID. The registration ID for the IoT device must match subject common name on its device certificate. If you followed the steps in this quickstart to generate a self-signed test certificate, my-x509-device is both the subject name and the registration ID for the device.

   set PROVISIONING_REGISTRATION_ID=my-x509-device
   

6. Set the environment variables for the device certificate and (unencrypted) device private key files.

   set CERTIFICATE_FILE=.\device-cert.pem
   set KEY_FILE=.\unencrypted-device-key.pem
   

7. Run the sample and verify that the device was provisioned successfully.

   node register_x509.js
   

   You should see output similar to the following example:

   registration succeeded
   assigned hub=contoso-hub-2.azure-devices.cn
   deviceId=my-x509-device
   Client connected
   send status: MessageEnqueued
   

In this section, you use your Windows command prompt.

1. In the Azure portal, select the Overview tab for your Device Provisioning Service.

2. Copy the ID Scope and Global device endpoint values.

   

3. In your Windows command prompt, go to the directory of the provision_x509.py sample. The path shown is relative to the location where you cloned the SDK.

   cd ./azure-iot-sdk-python/samples/async-hub-scenarios
   

   This sample uses six environment variables to authenticate and provision an IoT device using DPS. These environment variables are:

   Variable name	Description
   PROVISIONING_HOST	The global endpoint used for connecting to your DPS instance.
   PROVISIONING_IDSCOPE	The ID Scope for your DPS instance.
   DPS_X509_REGISTRATION_ID	The registration ID for your device. It must also match the subject name on the device certificate.
   X509_CERT_FILE	The path to your device certificate file.
   X509_KEY_FILE	The path to your device certificate private key file.
   PASS_PHRASE	The pass phrase you used to encrypt the certificate and private key file (1234).

4. Add the environment variables for the global device endpoint and ID Scope.

   set PROVISIONING_HOST=global.azure-devices-provisioning.net
   set PROVISIONING_IDSCOPE=<ID scope for your DPS resource>
   

5. Set the environment variable for the registration ID. The registration ID for the IoT device must match subject name on its device certificate. If you followed the steps in this quickstart to generate a self-signed test certificate, my-x509-device is both the subject name and the registration ID for the device.

   set DPS_X509_REGISTRATION_ID=my-x509-device
   

6. Set the environment variables for the certificate file, private key file, and pass phrase.

   set X509_CERT_FILE=./device-cert.pem
   set X509_KEY_FILE=./device-key.pem
   set PASS_PHRASE=1234
   

7. Review the code for provision_x509.py. If you're not using Python version 3.7 or later, make the code change mentioned here to replace asyncio.run(main()) and save your changes.

8. Run the sample. The sample connects to DPS, which provisions the device to an IoT hub. After the device is provisioned, the sample sends some test messages to the IoT hub.

   $ python azure-iot-sdk-python/samples/async-hub-scenarios/provision_x509.py
   RegistrationStage(RequestAndResponseOperation): Op will transition into polling after interval 2. Setting timer.
   The complete registration result is
   my-x509-device
   TestHub12345.azure-devices.cn
   initialAssignment
   null
   Will send telemetry from the provisioned device
   sending message #4
   sending message #7
   sending message #2
   sending message #8
   sending message #5
   sending message #9
   sending message #1
   sending message #6
   sending message #10
   sending message #3
   done sending message #4
   done sending message #7
   done sending message #2
   done sending message #8
   done sending message #5
   done sending message #9
   done sending message #1
   done sending message #6
   done sending message #10
   done sending message #3
   

In this section, you use both your Windows command prompt and your Git Bash prompt.

1. In the Azure portal, select the Overview tab for your Device Provisioning Service.

2. Copy the ID Scope and Global device endpoint values.

   

3. In your Windows command prompt, navigate to the sample project folder. The path shown is relative to the location where you cloned the SDK

   cd .\azure-iot-sdk-java\provisioning\provisioning-device-client-samples\provisioning-X509-sample
   

4. Enter the provisioning service and X.509 identity information in the sample code. This information is used during provisioning, for attestation of the simulated device, prior to device registration.

   1. Open the file .\src\main\java\samples\com\microsoft\azure\sdk\iot\ProvisioningX509Sample.java in your favorite editor.

   2. Update the following values with the ID Scope and Provisioning Service Global Endpoint that you copied previously.

      private static final String idScope = "[Your ID scope here]";
      private static final String globalEndpoint = "[Your Provisioning Service Global Endpoint here]";
      private static final ProvisioningDeviceClientTransportProtocol PROVISIONING_DEVICE_CLIENT_TRANSPORT_PROTOCOL = ProvisioningDeviceClientTransportProtocol.HTTPS;
      
      

   3. Update the value of the leafPublicPem constant string with the value of your certificate, device-cert.pem.

      The syntax of certificate text must follow the following pattern with no extra spaces or characters.

      private static final String leafPublicPem = "-----BEGIN CERTIFICATE-----\n" +
      "MIIFOjCCAyKgAwIBAgIJAPzMa6s7mj7+MA0GCSqGSIb3DQEBCwUAMCoxKDAmBgNV\n" +
          ...
      "MDMwWhcNMjAxMTIyMjEzMDMwWjAqMSgwJgYDVQQDDB9BenVyZSBJb1QgSHViIENB\n" +
      "-----END CERTIFICATE-----";        
      

      Updating this string value manually can be prone to error. To generate the proper syntax, you can copy and paste the following command into your Git Bash prompt, and press ENTER. This command generates the syntax for the leafPublicPem string constant value and writes it to the output.

      sed 's/^/"/;$ !s/$/\\n" +/;$ s/$/"/' device-cert.pem
      

      Copy and paste the output certificate text for the constant value.

   4. Update the string value of the leafPrivateKey constant with the unencrypted private key for your device certificate, unencrypted-device-key.pem.

      The syntax of the private key text must follow the following pattern with no extra spaces or characters.

      private static final String leafPrivateKey = "-----BEGIN PRIVATE KEY-----\n" +
      "MIIJJwIBAAKCAgEAtjvKQjIhp0EE1PoADL1rfF/W6v4vlAzOSifKSQsaPeebqg8U\n" +
          ...
      "X7fi9OZ26QpnkS5QjjPTYI/wwn0J9YAwNfKSlNeXTJDfJ+KpjXBcvaLxeBQbQhij\n" +
      "-----END PRIVATE KEY-----";
      

      Updating this string value manually can be prone to error. To generate the proper syntax, you can copy and paste the following command into your Git Bash prompt, and press ENTER. This command generates the syntax for the leafPrivateKey string constant value and writes it to the output.

      sed 's/^/"/;$ !s/$/\\n" +/;$ s/$/"/' unencrypted-device-key.pem
      

      Copy and paste the output private key text for the constant value.

   5. Save your changes.

5. Build the sample, and then go to the target folder.

   mvn clean install
   cd target
   

6. The build outputs .jar file in the target folder with the following file format: provisioning-x509-sample-{version}-with-deps.jar; for example: provisioning-x509-sample-1.8.1-with-deps.jar. Execute the .jar file. You may need to replace the version in the following command.

   java -jar ./provisioning-x509-sample-1.8.1-with-deps.jar
   

   The sample connects to DPS, which provisions the device to an IoT hub. After the device is provisioned, the sample sends some test messages to the IoT hub.

   Starting...
   Beginning setup.
   WARNING: sun.reflect.Reflection.getCallerClass is not supported. This will impact performance.
   2022-05-11 09:42:05,025 DEBUG (main) [com.microsoft.azure.sdk.iot.provisioning.device.ProvisioningDeviceClient] - Initialized a ProvisioningDeviceClient instance using SDK version 2.0.0
   2022-05-11 09:42:05,027 DEBUG (main) [com.microsoft.azure.sdk.iot.provisioning.device.ProvisioningDeviceClient] - Starting provisioning thread...
   Waiting for Provisioning Service to register
   2022-05-11 09:42:05,030 INFO (global.azure-devices-provisioning.net-6255a8ba-CxnPendingConnectionId-azure-iot-sdk-ProvisioningTask) [com.microsoft.azure.sdk.iot.provisioning.device.internal.task.ProvisioningTask] - Opening the connection to device provisioning service...
   2022-05-11 09:42:05,252 INFO (global.azure-devices-provisioning.net-6255a8ba-Cxn6255a8ba-azure-iot-sdk-ProvisioningTask) [com.microsoft.azure.sdk.iot.provisioning.device.internal.task.ProvisioningTask] - Connection to device provisioning service opened successfully, sending initial device registration message
   2022-05-11 09:42:05,286 INFO (global.azure-devices-provisioning.net-6255a8ba-Cxn6255a8ba-azure-iot-sdk-RegisterTask) [com.microsoft.azure.sdk.iot.provisioning.device.internal.task.RegisterTask] - Authenticating with device provisioning service using x509 certificates
   2022-05-11 09:42:06,083 INFO (global.azure-devices-provisioning.net-6255a8ba-Cxn6255a8ba-azure-iot-sdk-ProvisioningTask) [com.microsoft.azure.sdk.iot.provisioning.device.internal.task.ProvisioningTask] - Waiting for device provisioning service to provision this device...
   2022-05-11 09:42:06,083 INFO (global.azure-devices-provisioning.net-6255a8ba-Cxn6255a8ba-azure-iot-sdk-ProvisioningTask) [com.microsoft.azure.sdk.iot.provisioning.device.internal.task.ProvisioningTask] - Current provisioning status: ASSIGNING
   Waiting for Provisioning Service to register
   2022-05-11 09:42:15,685 INFO (global.azure-devices-provisioning.net-6255a8ba-Cxn6255a8ba-azure-iot-sdk-ProvisioningTask) [com.microsoft.azure.sdk.iot.provisioning.device.internal.task.ProvisioningTask] - Device provisioning service assigned the device successfully
   IotHUb Uri : MyExampleHub.azure-devices.cn
   Device ID : java-device-01
   2022-05-11 09:42:25,057 INFO (main) [com.microsoft.azure.sdk.iot.device.transport.ExponentialBackoffWithJitter] - NOTE: A new instance of ExponentialBackoffWithJitter has been created with the following properties. Retry Count: 2147483647, Min Backoff Interval: 100, Max Backoff Interval: 10000, Max Time Between Retries: 100, Fast Retry Enabled: true
   2022-05-11 09:42:25,080 INFO (main) [com.microsoft.azure.sdk.iot.device.transport.ExponentialBackoffWithJitter] - NOTE: A new instance of ExponentialBackoffWithJitter has been created with the following properties. Retry Count: 2147483647, Min Backoff Interval: 100, Max Backoff Interval: 10000, Max Time Between Retries: 100, Fast Retry Enabled: true
   2022-05-11 09:42:25,087 DEBUG (main) [com.microsoft.azure.sdk.iot.device.DeviceClient] - Initialized a DeviceClient instance using SDK version 2.0.3
   2022-05-11 09:42:25,129 DEBUG (main) [com.microsoft.azure.sdk.iot.device.transport.mqtt.MqttIotHubConnection] - Opening MQTT connection...
   2022-05-11 09:42:25,150 DEBUG (main) [com.microsoft.azure.sdk.iot.device.transport.mqtt.Mqtt] - Sending MQTT CONNECT packet...
   2022-05-11 09:42:25,982 DEBUG (main) [com.microsoft.azure.sdk.iot.device.transport.mqtt.Mqtt] - Sent MQTT CONNECT packet was acknowledged
   2022-05-11 09:42:25,983 DEBUG (main) [com.microsoft.azure.sdk.iot.device.transport.mqtt.Mqtt] - Sending MQTT SUBSCRIBE packet for topic devices/java-device-01/messages/devicebound/#
   2022-05-11 09:42:26,068 DEBUG (main) [com.microsoft.azure.sdk.iot.device.transport.mqtt.Mqtt] - Sent MQTT SUBSCRIBE packet for topic devices/java-device-01/messages/devicebound/# was acknowledged
   2022-05-11 09:42:26,068 DEBUG (main) [com.microsoft.azure.sdk.iot.device.transport.mqtt.MqttIotHubConnection] - MQTT connection opened successfully
   2022-05-11 09:42:26,070 DEBUG (main) [com.microsoft.azure.sdk.iot.device.transport.IotHubTransport] - The connection to the IoT Hub has been established
   2022-05-11 09:42:26,071 DEBUG (main) [com.microsoft.azure.sdk.iot.device.transport.IotHubTransport] - Updating transport status to new status CONNECTED with reason CONNECTION_OK
   2022-05-11 09:42:26,071 DEBUG (main) [com.microsoft.azure.sdk.iot.device.DeviceIO] - Starting worker threads
   2022-05-11 09:42:26,073 DEBUG (main) [com.microsoft.azure.sdk.iot.device.transport.IotHubTransport] - Invoking connection status callbacks with new status details
   2022-05-11 09:42:26,074 DEBUG (main) [com.microsoft.azure.sdk.iot.device.transport.IotHubTransport] - Client connection opened successfully
   2022-05-11 09:42:26,075 INFO (main) [com.microsoft.azure.sdk.iot.device.DeviceClient] - Device client opened successfully
   Sending message from device to IoT Hub...
   2022-05-11 09:42:26,077 DEBUG (main) [com.microsoft.azure.sdk.iot.device.transport.IotHubTransport] - Message was queued to be sent later ( Message details: Correlation Id [54d9c6b5-3da9-49fe-9343-caa6864f9a02] Message Id [28069a3d-f6be-4274-a48b-1ee539524eeb] )
   Press any key to exit...
   2022-05-11 09:42:26,079 DEBUG (MyExampleHub.azure-devices.cn-java-device-01-ee6c362d-Cxn7a1fb819-e46d-4658-9b03-ca50c88c0440-azure-iot-sdk-IotHubSendTask) [com.microsoft.azure.sdk.iot.device.transport.IotHubTransport] - Sending message ( Message details: Correlation Id [54d9c6b5-3da9-49fe-9343-caa6864f9a02] Message Id [28069a3d-f6be-4274-a48b-1ee539524eeb] )
   2022-05-11 09:42:26,422 DEBUG (MQTT Call: java-device-01) [com.microsoft.azure.sdk.iot.device.transport.IotHubTransport] - IotHub message was acknowledged. Checking if there is record of sending this message ( Message details: Correlation Id [54d9c6b5-3da9-49fe-9343-caa6864f9a02] Message Id [28069a3d-f6be-4274-a48b-1ee539524eeb] )
   2022-05-11 09:42:26,425 DEBUG (MyExampleHub.azure-devices.cn-java-device-01-ee6c362d-Cxn7a1fb819-e46d-4658-9b03-ca50c88c0440-azure-iot-sdk-IotHubSendTask) [com.microsoft.azure.sdk.iot.device.transport.IotHubTransport] - Invoking the callback function for sent message, IoT Hub responded to message ( Message details: Correlation Id [54d9c6b5-3da9-49fe-9343-caa6864f9a02] Message Id [28069a3d-f6be-4274-a48b-1ee539524eeb] ) with status OK
   Message sent!