Application-Level Certificates

Last modified: January 23, 2026

Introduction

Mendix Cloud supports adding custom domains, such as https://myapp.mycompany.com, to your application environments. Each custom domain must be secured with an SSL/TLS certificate to enable HTTPS connections.

This document describes how Technical Contacts can configure and manage application-level (local) certificates for their apps.

This how-to explains how to do the following:

  • Generate a certificate request (CSR)
  • Upload an application-level certificate to Mendix Cloud
  • Renew an application-level certificate

Prerequisites

Before starting this how-to, you need to have the following prerequisites:

  • Basic knowledge of DNS (Domain Name System)
  • Basic knowledge of SSL/TLS certificates:
    • What is an SSL/TLS certificate and what it is used for?
    • What is an intermediate certificate chain and what it is used for?
    • What is an SSL/TLS private key and what it is used for?
    • What is a certificate request and what it is used for?
  • Basic knowledge of certificate authorities (such as GeoTrust, Thawte, Verisign, RapidSSL, GoDaddy, Comodo)

Managing Custom Domain Certificates in Mendix Cloud

A Mendix application can have multiple certificates. To manage application-level certificates, follow these steps:

  1. From Apps, go to the Environments page of your app.
  2. Click Cloud Settings ( ) from any of the available tabs to open the Manage Cloud Settings page.
  3. Switch to the Custom Domains tab.

If you already have a signed SSL/TLS certificate, skip to Uploading Your Own Custom Domain Certificate 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 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

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

  1. Click Request Certificate in the Custom Domains tab.

  2. In the Request Certificate wizard:

    1. Review the information in General Info, then click Next.
    2. Complete the required fields in Generate, then click Next.
    3. In PEM Format, an SSL/TLS private key and a certificate request are generated and displayed in PEM (Privacy-Enhanced Mail) format.

Once the CSR is generated, its 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 until the CSR is signed. The Local/Central column indicates whether the certificate is managed locally at the application level or centrally; in this case, it will display Local.

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

Uploading a Signed Certificate

Once you have a signed SSL/TLS certificate, you can upload it at the application-level by following these steps:

  1. Switch to the Custom Domains tab.

  2. Click the More Options ( ) icon on the CSR of interest.

  3. Select Details.

  4. Click Upload Signed Certificate.

  5. Add a Description of your certificate.

  6. Paste the signed TLS Certificate (in PEM format).

  7. Paste an Intermediate Certificate Chain. While optional for modern browsers, it is mandatory for programmatic access and service consumption (like OData services). The intermediate certificate chain is provided by your certificate authority.

  8. Click Save to complete the process.

You can now configure your custom domain. See Configuring a Custom Domain.

Uploading Your Own Custom Domain Certificate

To upload an application-level custom domain certificate, you need to have the following prepared:

  • An SSL/TLS certificate that is self-signed or signed by your certificate authority
  • An intermediate certificate chain provided by your certificate authority
  • An SSL/TLS private key

To upload the custom domain certificate, follow these steps:

  1. Click Upload Certificate in the Custom Domains tab.

  2. In the Upload Certificate wizard:

    1. Review the information in General Info, then click Next.
    2. Complete the required fields in Upload:
      • Add a Description for the certificate.
      • Paste the signed TLS Certificate.
      • Paste an Intermediate Certificate Chain. While optional for modern browsers, it is mandatory for programmatic access and service consumption (like OData services). The intermediate certificate chain is provided by your certificate authority.
      • Paste the TLS Private Key.
  3. Click Save to upload your new custom domain certificate to Mendix Cloud automatically.

Once the certificate is uploaded, you can configure your custom domain. For instructions, refer to Configuring a Custom Domain.

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.

Renewing a Custom Domain Certificate

Custom domain certificates have an expiry date. There are two methods for renewing an application-level custom domain certificate that is about to expire:

  • Create a new custom domain certificate (recommended)

  • Update an existing custom domain certificate

You can handle an expiring domain certificate by replacing it with a new one. You can do this in one of two ways:

You can now select the new certificate for your custom domain (for more information, see Configuring a Custom Domain).

Method 2: Renewing by Updating an Existing Custom Domain Certificate

You can do this by editing an existing application-level custom domain certificate. To update an existing custom domain certificate, follow these steps:

  1. Click the More Options ( ) icon on the CSR of interest.
  2. Select Edit.
  3. Paste the signed TLS Certificate.
  4. Paste an Intermediate Certificate Chain. While optional for modern browsers, it is mandatory for programmatic access and service consumption (like OData services). The intermediate certificate chain is provided by your certificate authority.