From 530203b5b2fefeed576269b10f75e91ba6e4fc66 Mon Sep 17 00:00:00 2001 From: Steven Martin Date: Wed, 18 Dec 2024 22:55:52 -0500 Subject: [PATCH 1/3] docs: update tls cert private instrs --- docs/pages/includes/tls-certificate-setup.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/pages/includes/tls-certificate-setup.mdx b/docs/pages/includes/tls-certificate-setup.mdx index dbda51e063e42..cfadb22e87202 100644 --- a/docs/pages/includes/tls-certificate-setup.mdx +++ b/docs/pages/includes/tls-certificate-setup.mdx @@ -30,7 +30,8 @@ deployments, use your own private key and certificate. On your Teleport host, place a valid private key and a certificate chain in `/var/lib/teleport/privkey.pem` and `/var/lib/teleport/fullchain.pem` respectively. - The leaf certificate must have a subject that corresponds to the domain of your Teleport host, e.g., `*.teleport.example.com`. + The leaf certificate must have a subject that corresponds to the domain of your Teleport host, e.g., `teleport.example.com` + with mapped sub-domains as alternate names, e.g.. `*.teleport.example.com`. On the host where you will start the Teleport Auth Service and Proxy Service, run the following `teleport configure` command. Assign Date: Thu, 19 Dec 2024 07:39:52 -0500 Subject: [PATCH 2/3] doc: correct comma placement --- docs/pages/includes/tls-certificate-setup.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/includes/tls-certificate-setup.mdx b/docs/pages/includes/tls-certificate-setup.mdx index cfadb22e87202..0794ee581ee21 100644 --- a/docs/pages/includes/tls-certificate-setup.mdx +++ b/docs/pages/includes/tls-certificate-setup.mdx @@ -31,7 +31,7 @@ deployments, use your own private key and certificate. and `/var/lib/teleport/fullchain.pem` respectively. The leaf certificate must have a subject that corresponds to the domain of your Teleport host, e.g., `teleport.example.com` - with mapped sub-domains as alternate names, e.g.. `*.teleport.example.com`. + with mapped sub-domains as alternate names, e.g., `*.teleport.example.com`. On the host where you will start the Teleport Auth Service and Proxy Service, run the following `teleport configure` command. Assign Date: Thu, 19 Dec 2024 16:09:45 -0500 Subject: [PATCH 3/3] docs: verbiage update --- docs/pages/includes/tls-certificate-setup.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/includes/tls-certificate-setup.mdx b/docs/pages/includes/tls-certificate-setup.mdx index 0794ee581ee21..538b7cac6a1fd 100644 --- a/docs/pages/includes/tls-certificate-setup.mdx +++ b/docs/pages/includes/tls-certificate-setup.mdx @@ -31,7 +31,7 @@ deployments, use your own private key and certificate. and `/var/lib/teleport/fullchain.pem` respectively. The leaf certificate must have a subject that corresponds to the domain of your Teleport host, e.g., `teleport.example.com` - with mapped sub-domains as alternate names, e.g., `*.teleport.example.com`. + with all other mapped domains as alternate names, e.g., `*.teleport.example.com` for web applications. On the host where you will start the Teleport Auth Service and Proxy Service, run the following `teleport configure` command. Assign