Mention unstable Common Name (CN) in TLS certs (platformsh#4148)

* Mention unstable Common Name (CN) in TLS certs * Add to Upsun side as well --------- Co-authored-by: Chad Carlson <[email protected]>
Amazinggrace07 · Aug 27, 2024 · f788aa3 · f788aa3
1 parent de33fd1
commit f788aa3
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 0 deletions.
diff --git a/sites/platform/src/define-routes/https.md b/sites/platform/src/define-routes/https.md
@@ -38,6 +38,9 @@ If you need more hostnames, you can obtain additional certificates
 or a wildcard certificate from a [third-party issuer](../domains/steps/tls.md).
 Alternatively, consider splitting your project up into multiple {{% vendor/name %}} projects.
 
+Please note that when using multiple domains, the Common Name (CN) to which the certificate is issued to
+is not guaranteed to be the same on each certificate renewal.
+
 ### Certificate renewals
 
 When you use the [TLS certificates](#tls-certificates) provided by {{% vendor/name %}},

diff --git a/sites/upsun/src/define-routes/https.md b/sites/upsun/src/define-routes/https.md
@@ -38,6 +38,9 @@ If you need more hostnames, you can obtain additional certificates
 or a wildcard certificate from a [third-party issuer](../domains/steps/tls.md).
 Alternatively, consider splitting your project up into multiple {{% vendor/name %}} projects.
 
+Please note that when using multiple domains, the Common Name (CN) to which the certificate is issued to
+is not guaranteed to be the same on each certificate renewal.
+
 ### Certificate renewals
 
 When you use the [TLS certificates](#tls-certificates) provided by {{% vendor/name %}},