You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{% 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 %}}
108
104
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.
110
106
111
107
You can now go to your certificate authority to get a signed SSL/TLS certificate.
112
108
@@ -156,21 +152,16 @@ To upload a custom domain certificate, you need to have the following things pre
156
152
157
153
To upload the custom domain certificate, follow these steps:
158
154
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.
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**.
172
163
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.
174
165
175
166
{{% 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 %}}
Copy file name to clipboardExpand all lines: content/en/docs/deployment/mendix-cloud-deploy/environments.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -129,8 +129,9 @@ The **Create a Package** wizard walks you through creating deployment packages.
129
129
1. On the [Deployment Packages](#deployment-packages-tab) tab, click **Create a Package**. This launches the **Create Package** wizard.
130
130
2. On the **Select Branch** tab, select the branch on which to base the build.
131
131
3. On the **Select Revision** tab, select the branch revision on which to base the package.
132
-
4. On the **Choose a Tag** tab, specify the version tag. This includes the major, minor, and patch version numbers.
133
-
5. Click **Build this revision**.
132
+
4. On the **Other Options** tab, add the version tag. This tag should include the major and minor version numbers, patch, and revision.
133
+
5. Add a tag description.
134
+
6. Click **Build this revision**.
134
135
135
136
#### Uploading a Package {#upload-package}
136
137
@@ -191,7 +192,7 @@ If you click **Cloud Settings** ({{< icon name="settings-slider-1" >}}) from any
191
192
192
193
### Custom Domains
193
194
194
-
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.
195
196
196
197
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/).
0 commit comments