> For the complete documentation index, see [llms.txt](https://developers.make.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.make.com/custom-apps-documentation/other/https-custom-ca.md).

# HTTPS self-signed or with custom CA

Connect securely to HTTPS services using self-signed or custom CA certificates.

**This guide is relevant only for special cases where it is reasonably expected that the application may need to communicate with third-party servers using HTTPS connections that rely on either a self-signed certificate or a custom certificate authority (CA) instead of a widely trusted public CA.**

**If your custom app only interacts with services that use publicly trusted certificates, you can safely ignore this guide.**

***

{% hint style="warning" %}
**BREAKING CHANGE** – Coming October 26, 2026

We would like to inform you in advance about an upcoming change that will strengthen our HTTPS validation policy.

Beginning on October 26, 2026, Make will begin **blocking untrusted HTTPS connections by default**.

If your servers are using self-signed or otherwise untrusted certificates, please carefully review the guide below and update your custom app accordingly.

While this change may affect a small number of edge-case usages, we are confident that it brings a clear security benefit to all customers.
{% endhint %}

***

## Solution

Your custom app can be extended to accept a custom certificate (trusted CA or self-signed). A certificate issued by a globally trusted CA is preferred.

There are two options to choose from:

* [Define the certificate statically](#define-certificate-statically)
* [Ask the user for the certificate dynamically](#ask-user-for-certificate-dynamically)

{% hint style="info" %}
**Which certificate to use**

* For a self-signed certificate, use the server's own certificate.
* For a certificate issued by a private CA, use the certificate of the root CA. The server's own certificate or an intermediate certificate is not enough.

To learn how to get the certificate, see [Get the certificate](https://developers.make.com/custom-apps-documentation/other/fix-https-certificate-errors-in-scenarios.md#get-the-certificate).
{% endhint %}

### Define certificate statically

Add the trusted custom CA certificate (or self-signed certificate) to both the `base` and `connection` JSON configurations of the custom app.

You need to add the certificate in both places, because connections do not inherit configuration from the base code.

**Custom app: Base**

```jsonc
// custom app's base
{
    // Your default base config like `baseUrl`, `headers`, `response`, `log`, ...
    "baseUrl": "https://some-my-private-service.example.com/api",

    // Add the property `ca` with public cert of your own CA or of your self-signed cert.
    "ca": "-----BEGIN CERTIFICATE-----\nMIIDeTCCAmGgAwIBAgIJAOSe0iZEklcXMA0GCSqGSIb3DQEBCwUAMGIxCzAJBgNV\nBAYTAlVTMRMwEQYDVQQIDApDYWxpZm9ybmlhMRYwFAYDVQQHDA1TYW4gRnJhbmNp\n... (certificate truncated in example) ...\ny4qocoQVErLCN+R1VscdmTgNgIypce6+Dirco8Skh5/V7KgLXHUZ7BPyaxJpzxxM\nvJEZ/1G0g7NopNIOKcCBBneqjir85QUYQ9DZDNY=\n-----END CERTIFICATE-----"
}
```

**Connection: Communication**

```jsonc
// connection's communication
{
    "ca": "-----BEGIN CERTIFICATE-----\nMIIDeTCCAmGgAwI ...", // certificate truncated in example

    // ... and other config like `url`, `headers`, `response`.
}
```

{% hint style="info" %}
The examples above show the principle of how to configure it. But defining the CA cert statically is useful in limited cases, where the certificate is fixed and known in advance.
{% endhint %}

### Ask user for certificate dynamically

Let the customer enter the certificate themselves during the connection creation. This is useful if you need to give your custom app the flexibility to connect to any instance on the internet (for example, by having the customer enter their own URL).

For the implementation, add a new `mappable parameter` with `type: "cert"` into the Connection and then reference it in both the base and the connection's communication.

**1. Connection: Parameters** – ask the user for the certificate

```jsonc
// connection's mappable parameters
[
    // Ask user for extra CA of HTTPS connection
    {
        "name": "ca",
        "label": "Trusted Custom CA / Self-Signed Certificate",
        "help": "Upload a certificate if an HTTPS server uses custom Certificate Authority (CA) or a self-signed certificate. This allows to trust connections to that server.",
        "type": "cert",
        "advanced": true, // display only after click to "Show advanced settings"
        "editable": true, // allow to enable/disable in connection edit

    },
]
```

**2. Connection: Communication** – use the certificate in the connection

```jsonc
// connection's communication
{
    // use the user uploaded certificate in the Connection
    "ca": "{{connection.ca}}",

    // ... other config like `url`, `headers`, `response`.
}
```

**3. Custom app: Base** – use the certificate in the rest of the custom app

```jsonc
// custom app's base
{
    // use the user uploaded certificate in the rest of custom app
    "ca": "{{connection.ca}}",

    // ... and other config like `baseUrl`, `headers`, `response`.
}
```

If the user leaves the certificate field empty, Make verifies the server against the publicly trusted CAs as usual.

### OAuth 2.0 connections

The connection examples above are for a basic connection, where the communication is a single request. In OAuth 2.0 connections, the communication consists of several requests (`preauthorize`, `token`, `refresh`, `info`, `invalidate`), and Make sends each of them with its own configuration. Add `ca` to every request that goes to the server with the custom certificate. A `ca` at the top level of the communication has no effect.

The `authorize` step only redirects the user's browser to the server. Make does not send this request, so `ca` has no effect there.

**Connection: Communication**

```jsonc
// connection's communication
{
    "authorize": {
        // redirects the user's browser, `ca` has no effect here
        "url": "https://some-my-private-service.example.com/oauth/authorize",
        // ...
    },
    "token": {
        "url": "https://some-my-private-service.example.com/oauth/token",
        "ca": "{{connection.ca}}",
        // ...
    },
    "refresh": {
        "url": "https://some-my-private-service.example.com/oauth/token",
        "ca": "{{connection.ca}}",
        // ...
    },
    "info": {
        "url": "https://some-my-private-service.example.com/api/me",
        "ca": "{{connection.ca}}",
        // ...
    }
}
```

The example uses the certificate entered by the user. If you define the certificate statically, use the certificate string instead of `{{connection.ca}}`.

### Use the certificate only for the server that needs it

When a request has `ca` filled in, Make trusts only the certificates in `ca` field for that request. Certificates issued by publicly trusted CAs are then rejected as untrusted. Therefore, keep the following in mind:

* If your app also calls a server with a publicly trusted certificate, for example a public OAuth provider or a file storage, use `ca` only in the modules, RPCs, or connections that make requests to the server with the custom certificate.
* If the server later switches to a publicly trusted certificate, connections with a previously filled `ca` fail. Users must remove the certificate from the connection. With a statically defined certificate, you need to update the custom app.

## Common certificate issues

For the list of certificate error codes, what they mean, and how to fix them, see [Fix HTTPS certificate errors in scenarios](https://developers.make.com/custom-apps-documentation/other/fix-https-certificate-errors-in-scenarios.md#certificate-error-codes).

***

## Behavior quick reference guide

### Behavior until October 25, 2026

By default, Make **allows** connections to HTTPS services even when the certificate is invalid or untrusted. In such cases, the platform **generates a warning** for each affected scenario module.

<table><thead><tr><th valign="top">Certificate Issue</th><th valign="top">Default Behavior</th></tr></thead><tbody><tr><td valign="top">✅ Public HTTPS certificate</td><td valign="top">✅ Connection allowed</td></tr><tr><td valign="top">❗ Self-signed certificate</td><td valign="top">🔔 Connection allowed, produces warning</td></tr><tr><td valign="top">❗ Custom CA certificate</td><td valign="top">🔔 Connection allowed, produces warning</td></tr><tr><td valign="top">❗ Expired certificate</td><td valign="top">🔔 Connection allowed, produces warning</td></tr><tr><td valign="top">❗ Invalid or weak certificate</td><td valign="top">🔔 Connection allowed, produces warning</td></tr></tbody></table>

### Behavior from October 26, 2026 (breaking change)

Starting from this date, Make will **block** HTTPS connections by default if the certificate is untrusted or invalid. To maintain functionality, follow the recommended steps in your custom app:

<table><thead><tr><th valign="top">Certificate Issue</th><th valign="top">Default Behavior</th><th valign="top">Recommended Custom App improvement</th><th valign="top">Behavior After the Custom app improvement</th></tr></thead><tbody><tr><td valign="top">✅ Public HTTPS certificate</td><td valign="top">✅ Connection allowed</td><td valign="top">✅ No action needed</td><td valign="top">✅ Connection allowed</td></tr><tr><td valign="top">❗ Self-signed certificate</td><td valign="top">❌ Connection blocked</td><td valign="top">🔧 <a href="#solution">Upload the self-signed certificate</a></td><td valign="top">✅ Connection allowed</td></tr><tr><td valign="top">❗ Custom CA certificate</td><td valign="top">❌ Connection blocked</td><td valign="top">🔧 <a href="#solution">Upload the custom CA certificate</a></td><td valign="top">✅ Connection allowed</td></tr><tr><td valign="top">❗ Expired certificate</td><td valign="top">❌ Connection blocked</td><td valign="top">❌ No fix in Custom App is possible</td><td valign="top">❌ Connection blocked</td></tr><tr><td valign="top">❗ Invalid or weak certificate</td><td valign="top">❌ Connection blocked</td><td valign="top">❌ No fix in Custom App is possible</td><td valign="top">❌ Connection blocked</td></tr></tbody></table>

***

## HTTPS with invalid or expired certificate

Due to security implications, it is not possible to configure the custom app to connect to an HTTPS service if the certificate is **invalid** or **expired**.

The only secure solution in this case is to **replace the invalid or expired certificate** on the server. This process lies outside of Make's control and must be coordinated directly with the third-party technical support team responsible for the affected server.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers.make.com/custom-apps-documentation/other/https-custom-ca.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
