Merge pull request mendix#9737 from mendix/olu-custom-domain-update

Updating doc with new info

Author: OlufunkeMoronfolu

content/en/docs/deployment/mendix-cloud-deploy/custom-domains.md

@@ -10,7 +10,7 @@ aliases:
     - /howtogeneral/mendixcloud/custom-domains
 #To update these screenshots, you can log in with credentials detailed in How to Update Screenshots Using Team Apps.
 #If moving or renaming this doc file, implement a temporary redirect and let the respective team know they should update the URL in the product. See Mapping to Products for more details.
-#Linked from Mendix Portal > Environments > Custom Domains
+#Linked from Mendix Portal > Environments > Cloud Settings > Custom Domains
 ---
 
 ## Introduction
@@ -20,10 +20,6 @@ Mendix Cloud supports adding custom domains such as `https://myapp.mycompany.com
 {{% alert color="info" %}}This page describes certificates for incoming connections. For information on setting up certificates for outgoing connections, see [Certificates](/developerportal/deploy/certificates/).
 {{% /alert %}}
 
-{{% alert color="info" %}}
-Changes that affect DNS routing may not display immediately. This is because of DNS caching, where changes are not visible until the cache is updated.
-{{% /alert %}}
-
 This how-to explains how to do the following:
 
 * Generate a certificate request for your custom domain
@@ -52,7 +48,11 @@ Custom domains can be added only to licensed apps. You cannot add custom domains
 
 ### Create and Configure a CNAME Record{#DNS}
 
-Before configuring your custom domain in Mendix Cloud, you need to configure a DNS record for your custom domain with your domain registrar or DNS provider.
+{{% alert color="info" %}}
+Changes that affect DNS routing may not display immediately. This is because of DNS caching, where changes are not visible until the cache is updated.
+{{% /alert %}}
+
+Before configuring your custom domain in Mendix Cloud, you need to set up a DNS record for your custom domain with your domain registrar or DNS provider.
 
 Create a CNAME (Canonical Name) record and point it to `[YOUR-CUSTOM-DOMAIN].cname.mendix.net.`. For example, if your custom domain is `myapp.mycompany.com`, create a CNAME record pointing to `myapp.mycompany.com.cname.mendix.net.` so that Mendix can direct your custom domain to your Mendix app.
 
@@ -73,15 +73,16 @@ You can choose which certificate to use when you configure a custom domain for a
 To manage custom domains, follow these steps:
 
 1. From [Apps](https://sprintr.home.mendix.com), go to the **Environments** page of your app.
-1. Switch to the **Custom Domains** tab.
+2. Click **Cloud Settings** ({{< icon name="settings-slider-1" >}}) from any of the [available tabs](/developerportal/deploy/environments/#available-tabs) to open the **Manage Cloud Settings** page.
+3. Switch to the **Custom Domains** tab.
 
-    {{< figure src="/attachments/deployment/mendix-cloud-deploy/custom-domains/custom-domains-tab.png" class="no-border" >}}
-
-If you already have a signed SSL/TLS certificate, skip to [Uploading Your Own Custom Domain Certificate](#Uploading), below.
+If you already have a signed SSL/TLS certificate, skip to [Uploading Your Own Custom Domain Certificate](#Uploading) below.
 
 ## Obtaining a New Signed Certificate
 
-If you do not have an SSL/TLS certificate, you can order one from a certificate authority (such as GeoTrust, Thawte, Verisign, RapidSSL, GoDaddy, or Comodo). To get a signed SSL/TLS certificate from a certificate authority, you need to provide a certificate signing request (CSR). A private SSL/TLS key and a CSR tied to that key can be created in Mendix Cloud for you.
+If you do not have an SSL/TLS certificate, you can order one from a certificate authority (such as GeoTrust, Thawte, Verisign, RapidSSL, GoDaddy, or Comodo). To get a signed SSL/TLS certificate from a certificate authority, you need to provide a certificate signing request (CSR).
+
+A private SSL/TLS key and a CSR tied to that key can be created in Mendix Cloud for you.
 
 ### Generating a Certificate Request for your Custom Domain{#Generating}
 
@@ -91,45 +92,55 @@ Certificates are applied to a single app. Therefore, Mendix recommends that you
 
 To create a CSR and an RSA (Rivest–Shamir–Adleman) encryption key, follow these steps:
 
-1. Click **New** in the **Custom Domains** tab.
+1. Click **New Certificate** in the **Custom Domains** tab.
 
 2. Click **Create a Certificate Request**.
 
-    {{< figure src="/attachments/deployment/mendix-cloud-deploy/custom-domains/new-custom-domain.png" alt="" width=75% >}}
-
 3. Fill in the required fields.
 
 4. Click **Generate**.
 
-    {{< figure src="/attachments/deployment/mendix-cloud-deploy/custom-domains/generate-cert-req.png" width=60% class="no-border" >}}
 
     An SSL/TLS private key and a certificate request is generated. The certificate request will be shown in PEM (Privacy-Enhanced Mail) format.
 
-    {{< figure src="/attachments/deployment/mendix-cloud-deploy/custom-domains/pem-format.png" class="no-border" >}}
+    {{< figure src="/attachments/deployment/mendix-cloud-deploy/custom-domains/new-pem-format.png" >}}
 
     {{% alert color="info" %}}The SSL/TLS private key will be hidden after you upload it. To keep the key secure, it will be stored in Mendix Cloud's secure keystore; it will not be available for download, and it cannot be obtained by Mendix Support.{{% /alert %}}
 
+On successful CSR generation, your CSR name appears in the table on the **Custom Domain** tabs. In the **Description** column, the name you provided during creation is followed by **Pending Customer Feedback**. This suffix remains as long as the CSR is open and not yet signed with a certificate.
+
 You can now go to your certificate authority to get a signed SSL/TLS certificate.
 
 ### Uploading a Signed Certificate{#Upload}
 
 Once you have a signed SSL/TLS certificate, you can upload it by following these steps:
 
-1. In the **Custom Domains** tab, select the custom domain certificate that you want to upload.
+1. Switch to the **Custom Domains** tab.
+
+2. Click the **More Options** ({{% icon name="three-dots-menu-horizontal" %}}) icon on the CSR of interest.
 
-2. Click **Upload Signed Certificate**. 
+3. Select **Details**.
 
-    {{< figure src="/attachments/deployment/mendix-cloud-deploy/custom-domains/certificate.png" class="no-border" >}}
+4. Click **Upload Signed Certificate**. 
 
-3. Add a **Description** of your certificate.
+5. Add a **Description** of your certificate.
 
-4. Paste the signed **TLS Certificate** (in PEM format).
+6. Paste the signed **TLS Certificate** (in PEM format).
 
-5. Paste an **Intermediate Certificate Chain**. This is optional, but highly recommended. The intermediate certificate chain is provided by your certificate authority.
+7. Paste an **Intermediate Certificate Chain**. This is optional, but highly recommended. The intermediate certificate chain is provided by your certificate authority.
 
     {{< figure src="/attachments/deployment/mendix-cloud-deploy/custom-domains/signed-certificate.png" width=80% class="no-border" >}}
 
-    {{% alert color="warning" %}}The intermediate certificates of the main certificate authorities are included in the built-in CA databases of modern browsers. Therefore, you do not need to include an intermediate certificate to serve your website through SSL/TLS to users of modern browsers. However, you cannot predict how your users will attempt to connect to your website; not including an intermediate certificate may result in connection issues for some users. Tools such as curl do not recognize intermediate certificates automatically. Because of this, intermediate certificates are highly recommended but optional.{{% /alert %}}
+8. Click **Save** to complete the process.
+
+{{% alert color="warning" %}}
+The intermediate certificates of the main certificate authorities are included in the built-in CA databases of modern browsers. Therefore, you do not need to include an intermediate certificate to serve your website through SSL/TLS to users of modern browsers. 
+
+However, you cannot predict how your users will attempt to connect to your website; not including an intermediate certificate may result in connection issues for some users.
+
+Tools such as curl do not recognize intermediate certificates automatically. Because of this, intermediate certificates are highly recommended but optional.
+    
+{{% /alert %}}
 
 You can now configure your custom domain. See [Configuring a Custom Domain](#Configuring), below.
 
@@ -143,11 +154,9 @@ To upload a custom domain certificate, you need to have the following things pre
 
 To upload the custom domain certificate, follow these steps:
 
-1. Click **New** in the **Custom Domains** tab.
+1. Click **New Certificate** in the **Custom Domains** tab.
 
-2. Click **Upload Certificate, Chain and Key**.
-
-    {{< figure src="/attachments/deployment/mendix-cloud-deploy/custom-domains/new-custom-domain.png" width=75% alt="" >}}
+2. Click **Upload Certificate**.
 
 3. Type a **Description** for the certificate.
 
@@ -167,8 +176,6 @@ You can now configure your custom domain. For details, see [Configuring a Custom
 
 You can add as many certificates as you need. Each certificate will be listed with the description you gave it. Make sure to give them meaningful names so that you can identify them easily.
 
-{{< figure src="/attachments/deployment/mendix-cloud-deploy/custom-domains/certificate-list.png" alt="List of certificates" class="no-border" >}}
-
 ## Renewing a Custom Domain Certificate
 
 Custom domain certificates have an expiry date. There are two methods for renewing a custom domain certificate that is about to expire:
@@ -193,9 +200,12 @@ If you are rotating a certificate, you do not need to remove the current domain
 
 ### Method 2: Renewing by Updating an Existing Custom Domain Certificate
 
-You can also edit an existing custom domain certificate.
+You can do this by editing an existing custom domain certificate. To update an existing custom domain certificate, follow these steps:
 
-{{< figure src="/attachments/deployment/mendix-cloud-deploy/custom-domains/certificate-edit.png" alt="Edit a certificate" class="no-border" >}}
+1. Click the **More Options** ({{% icon name="three-dots-menu-horizontal" %}}) icon on the CSR of interest.
+2. Select **Edit**.
+3. Paste the signed **TLS Certificate**.
+4. Paste the **Intermediate Certificate Chain**. This is optional, but most browsers require it. The intermediate certificate chain is provided by your certificate authority.
 
 {{% alert color="warning" %}}
 To edit an existing custom domain certificate, you need the following:
@@ -214,23 +224,15 @@ To configure a custom domain for your application environment, follow these step
 
 2. Click **Details** ({{% icon name="notes-paper-edit" %}}) on the environment you want to configure.
 
-    {{< figure src="/attachments/deployment/mendix-cloud-deploy/custom-domains/environment-details.png" alt="The Details icon" >}}
-
-3. Go to the **Network** tab.
-
-    {{< figure src="/attachments/deployment/mendix-cloud-deploy/custom-domains/network.png" >}}
+3. On the **Environment Details** page, go to the **Network** tab.
 
-4. In the **Custom Domains** section, you can manage your custom domains.
+4. In the **Custom Domains** section, click **Add** to create a new custom domain (or **Edit** to edit an existing one).
 
-5. Click **Add** to create a new custom domain (or **Edit** to edit an existing one).
+5. Type the **Domain name**.
 
-6. Type the **Domain name**.
+6. Select a **Certificate** from the drop-down list of uploaded certificates.
 
-7. Select a **Certificate** from the drop-down list of uploaded certificates.
-
-8. Click **Save** to save your custom domain. It will be configured for your application environment automatically.
-
-    {{< figure src="/attachments/deployment/mendix-cloud-deploy/custom-domains/custom-domain.png" alt="" width=80% class="no-border" >}}
+7. Click **Save** to save your custom domain. It will be configured for your application environment automatically.
 
 {{% alert color="info" %}}
 Make sure you have configured a CNAME record for your custom domain with your domain registrar/DNS provider (for details, see [Create and Configure a CNAME Record](#DNS)), above.
@@ -254,11 +256,13 @@ To reach the root certificate, you must link your certificate via the intermedia
 
 ### How Do You Get my SAML Metadata or CommunityCommons.GetApplicationUrl to Use the Custom URL? {#use-custom-url}
 
-For certain use cases, it is important for the Mendix runtime to know the public URL of your applications. This is most commonly needed when your app generates links back to itself. To tell the runtime where it lives, set the `ApplicationRootUrl` [custom runtime setting](/refguide/custom-settings/#general). To set the custom runtime setting, follow the instructions in the [Custom Runtime Settings](/developerportal/deploy/environments-details/#custom-runtime-settings) section of *Environment Details*.
+For certain use cases, it is important for the Mendix runtime to know the public URL of your applications. This is most commonly needed when your app generates links back to itself.
+
+To tell the runtime where it lives, set the `ApplicationRootUrl` [custom runtime setting](/refguide/custom-settings/#general). To set the custom runtime setting, follow the instructions in the [Custom Runtime Settings](/developerportal/deploy/environments-details/#custom-runtime-settings) section of *Environment Details*.
 
 ### Can You Configure Multiple Custom Domains for the Same Application? {#multiple-custom-domains}
 
-Yes, you can configure multiple custom domains for the same application. Please note that this can only be done by [uploading multiple own custom domain certificates](#Uploading). You can only [generate one certificate signing request for one custom domain](#Generating) for your application.
+Yes, you can configure multiple custom domains for the same application. You can only do this by [uploading multiple own custom domain certificates](#Uploading). You can only [generate one certificate signing request for one custom domain](#Generating) for your application.
 
 ## Read More