Skip to content

Commit 1c1463a

Browse files
committed
Incorp, round 1
1 parent f68d977 commit 1c1463a

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

articles/iot-hub/.openpublishing.redirection.iot-hub.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1116,7 +1116,7 @@
11161116
{
11171117
"source_path_from_root": "/articles/iot-hub/tutorial-x509-scripts.md",
11181118
"redirect_url": "/azure/iot-hub/tutorial-x509-openssl",
1119-
"redirect_document_id": true
1119+
"redirect_document_id": false
11201120
}
11211121
]
11221122
}

articles/iot-hub/tutorial-x509-openssl.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,16 +14,16 @@ ms.custom: [mvc, 'Role: Cloud Development', 'Role: Data Analytics']
1414

1515
# Tutorial: Use OpenSSL to create test certificates
1616

17-
Although you can purchase X.509 certificates from a trusted certification authority, creating your own test certificate hierarchy is adequate for testing IoT Hub device authentication.
17+
For production environments, we recommend that you purchase an X.509 CA certificate from a public root certificate authority (CA). However, creating your own test certificate hierarchy is adequate for testing IoT Hub device authentication. For more information about getting an X.509 CA certificate from a public root CA, see the [Get an X.509 CA certificate](iot-hub-x509ca-overview.md#get-an-x509-ca-certificate) section of [Authenticate devices using X.509 CA certificates](iot-hub-x509ca-overview.md).
1818

19-
The following example uses [OpenSSL](https://www.openssl.org/) and the [OpenSSL Cookbook](https://www.feistyduck.com/library/openssl-cookbook/online/ch-openssl.html) to create a certification authority (CA), a subordinate CA, and a device certificate. The example then signs the subordinate CA and the device certificate into a certificate hierarchy. This example is presented for demonstration purposes only.
19+
The following example uses [OpenSSL](https://www.openssl.org/) and the [OpenSSL Cookbook](https://www.feistyduck.com/library/openssl-cookbook/online/ch-openssl.html) to create a certificate authority (CA), a subordinate CA, and a device certificate. The example then signs the subordinate CA and the device certificate into a certificate hierarchy. This example is presented for demonstration purposes only.
2020

2121
>[!NOTE]
2222
>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. The scripts are included with the [Azure IoT Hub Device SDK for C](https://github.com/Azure/azure-iot-sdk-c). The scripts are provided for demonstration purposes only. Certificates created by them must not be used for production. The certificates contain hard-coded passwords (“1234”) and expire after 30 days. You must use your own best practices for certificate creation and lifetime management in a production environment. For more information, see [Managing test CA certificates for samples and tutorials](https://github.com/Azure/azure-iot-sdk-c/blob/main/tools/CACertificates/CACertificateOverview.md) in the GitHub repository for the [Azure IoT Hub Device SDK for C](https://github.com/Azure/azure-iot-sdk-c).
2323
2424
## Step 1 - Create the root CA directory structure
2525

26-
Create a directory structure for the certification authority.
26+
Create a directory structure for the certificate authority.
2727

2828
* The *certs* directory stores new certificates.
2929
* The *db* directory stores the certificate database.

0 commit comments

Comments
 (0)