Skip to content

Commit 099c5d4

Browse files
Merge pull request #231064 from jlian/patch-89
Add IP address SAN config
2 parents 441d977 + edcc847 commit 099c5d4

File tree

1 file changed

+8
-6
lines changed

1 file changed

+8
-6
lines changed

articles/iot-edge/tutorial-configure-est-server.md

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Tutorial - Configure Enrollment over Secure Transport Server (EST) for Az
33
description: This tutorial shows you how to set up an Enrollment over Secure Transport (EST) server for Azure IoT Edge.
44
author: PatAltimore
55
ms.author: patricka
6-
ms.date: 01/05/2023
6+
ms.date: 03/16/2023
77
ms.topic: tutorial
88
ms.service: iot-edge
99
services: iot-edge
@@ -81,10 +81,12 @@ The Dockerfile uses Ubuntu 18.04, a [Cisco library called `libest`](https://gith
8181
# Setting the root CA expiration to 20 years
8282
RUN sed -i "s|-days 365|-days 7300 |g" ./createCA.sh
8383

84-
## If you want to host your EST server in the cloud (for example, an Azure Container Instance),
85-
## change myestserver.westus.azurecontainer.io to the fully qualified DNS name of your EST server
86-
## and uncomment the next line.
87-
# RUN sed -i "s|ip6-localhost|myestserver.westus.azurecontainer.io |g" ./ext.cnf
84+
## If you want to host your EST server remotely (for example, an Azure Container Instance),
85+
## change myestserver.westus.azurecontainer.io to the fully qualified DNS name of your EST server
86+
## OR, change the IP address
87+
## and uncomment the corresponding line.
88+
# RUN sed -i "s|DNS.2 = ip6-localhost|DNS.2 = myestserver.westus.azurecontainer.io|g" ./ext.cnf
89+
# RUN sed -i "s|IP.2 = ::1|IP.2 = <YOUR EST SERVER IP ADDRESS>|g" ./ext.cnf
8890

8991
# Set EST server certificate to be valid for 10 years
9092
RUN sed -i "s|-keyout \$EST_SERVER_PRIVKEY -subj|-keyout \$EST_SERVER_PRIVKEY -days 7300 -subj |g" ./createCA.sh
@@ -331,4 +333,4 @@ You can keep the resources and configurations that you created in this tutorial
331333
* Using username and password to bootstrap authentication to EST server isn't recommended for production. Instead, consider using long-lived *bootstrap certificates* that can be stored onto the device during manufacturing [similar to the recommended approach for DPS](../iot-hub/iot-hub-x509ca-concept.md). To see how to configure bootstrap certificate for EST server, see [Authenticate a Device Using Certificates Issued Dynamically via EST](https://github.com/Azure/iotedge/blob/main/edgelet/doc/est.md).
332334
* EST server can be used to issue certificates for all devices in a hierarchy as well. Depending on if you have ISA-95 requirements, it may be necessary to run a chain of EST servers with one at every layer or use the API proxy module to forward the requests. To learn more, see [Kevin's blog](https://kevinsaye.wordpress.com/2021/07/21/deep-dive-creating-hierarchies-of-azure-iot-edge-devices-isa-95-part-3/).
333335
* For enterprise grade solutions, consider: [GlobalSign IoT Edge Enroll](https://www.globalsign.com/en/iot-edge-enroll) or [DigiCert IoT Device Manager](https://www.digicert.com/iot/iot-device-manager)
334-
* To learn more about certificates, see [Understand how Azure IoT Edge uses certificates](iot-edge-certs.md).
336+
* To learn more about certificates, see [Understand how Azure IoT Edge uses certificates](iot-edge-certs.md).

0 commit comments

Comments
 (0)