Skip to content

Commit a91012d

Browse files
Merge pull request #10614 from mendix/olu-custom-domains-p9
Custom Domains new Ui doc
2 parents 34a40ae + 6c08762 commit a91012d

4 files changed

Lines changed: 17 additions & 26 deletions

File tree

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

Lines changed: 16 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -92,21 +92,17 @@ Certificates are applied to a single app. Therefore, Mendix recommends that you
9292

9393
To create a CSR and an RSA (Rivest–Shamir–Adleman) encryption key, follow these steps:
9494

95-
1. Click **New Certificate** in the **Custom Domains** tab.
95+
1. Click **Request Certificate** in the **Custom Domains** tab.
96+
2. In the **Request Certificate** wizard:
97+
1. Review the information in **General Info**, then click **Next**.
98+
2. Complete the required fields in **Generate**, then click **Next**.
99+
3. In **PEM Format**, an SSL/TLS private key and a certificate request are generated and displayed in PEM (Privacy-Enhanced Mail) format.
96100

97-
2. Click **Create a Certificate Request**.
98-
99-
3. Fill in the required fields.
100-
101-
4. Click **Generate**.
102-
103-
An SSL/TLS private key and a certificate request is generated. The certificate request will be shown in PEM (Privacy-Enhanced Mail) format.
104-
105-
{{< figure src="/attachments/deployment/mendix-cloud-deploy/custom-domains/new-pem-format.png" >}}
101+
{{< figure src="/attachments/deployment/mendix-cloud-deploy/custom-domains/pem-format.png" >}}
106102

107103
{{% 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 %}}
108104

109-
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.
105+
After the CSR is generated successfully, the CSR name appears in the table on the **Custom Domains** tab. In the **Certificate Description** column, the name you provided during creation is followed by **Pending Customer Feedback**. This suffix remains until the CSR is signed with a certificate. The **Local/Central** column also indicates whether the generated certificate is managed locally at the app level or centrally.
110106

111107
You can now go to your certificate authority to get a signed SSL/TLS certificate.
112108

@@ -156,21 +152,16 @@ To upload a custom domain certificate, you need to have the following things pre
156152

157153
To upload the custom domain certificate, follow these steps:
158154

159-
1. Click **New Certificate** in the **Custom Domains** tab.
160-
161-
2. Click **Upload Certificate**.
162-
163-
3. Type a **Description** for the certificate.
164-
165-
4. Paste the signed **TLS Certificate**.
166-
167-
5. Paste the **TLS Private Key**.
168-
169-
6. Paste an **Intermediate Certificate Chain**. While optional for modern browsers, it is mandatory for programmatic access and service consumption (like [OData services](/refguide/consumed-odata-services/)). The intermediate certificate chain is provided by your certificate authority.
170-
171-
{{< figure src="/attachments/deployment/mendix-cloud-deploy/custom-domains/new-certificate.png" width=60% class="no-border" >}}
155+
1. Click **Upload Certificate** in the **Custom Domains** tab.
156+
2. In the **Upload Certificate** wizard:
157+
1. Review the information in **General Info**, then click **Next**.
158+
2. Complete the required fields in **Upload**:
159+
* Add a **Description** for the certificate.
160+
* Paste the signed **TLS Certificate**.
161+
* Paste an **Intermediate Certificate Chain**. While optional for modern browsers, it is mandatory for programmatic access and service consumption (like [OData services](/refguide/consumed-odata-services/)). The intermediate certificate chain is provided by your certificate authority.
162+
* Paste the **TLS Private Key**.
172163

173-
7. Click **Save** to save your new custom domain certificate. It will be uploaded to Mendix Cloud automatically.
164+
3. Click**Save** to upload your new custom domain certificate to Mendix Cloud automatically.
174165

175166
{{% 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 %}}
176167

content/en/docs/deployment/mendix-cloud-deploy/environments.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -192,7 +192,7 @@ If you click **Cloud Settings** ({{< icon name="settings-slider-1" >}}) from any
192192

193193
### Custom Domains
194194

195-
On the **Custom Domains** tab, you can manage your custom domain certificates at the application level. You can also see an overview of linked custom domains.
195+
On the **Custom Domains** tab, the Technical Contact can manage custom domain certificates either centrally or at the application level. They can also access an overview of all the linked custom domains.
196196

197197
When you need your Mendix app to be accessible via your own URL (for example, `https://myapp.mycompany.com/`), you must provide a custom SSL/TLS certificate for your domain. This ensures a secure connection to your Mendix app. For more information, refer to [Custom Domains](/developerportal/deploy/custom-domains/).
198198

Binary file not shown.
77.9 KB
Loading

0 commit comments

Comments
 (0)