# Trusted Certificates

Add CA or self-signed certificates so the platform trusts your mail relay, SMS gateway, or provisioning target over TLS.

When the platform connects out over TLS to one of your own servers, it validates the server's certificate. **Trusted Certificates** is where you add the certificate authority (CA) or self-signed certificate that server presents, so the connection is trusted instead of rejected.

This trust applies to **outbound** connections only (the platform acting as the client, validating the *remote server's* certificate). It affects:

- your **mail relay** (a custom SMTP server),
- your **custom SMS gateway**,
- **outbound provisioning** to a SCIM target,
- a self-hosted **privacyIDEA** multi-factor server.

Endpoints that present a publicly trusted certificate (for example a commercial email or SMS API) work without any entry here.

> **Note:** Duo multi-factor authentication is not covered by this trust store. The Duo integration validates Duo's own cloud certificate directly and cannot be redirected to a different certificate authority. If your network performs TLS inspection (SSL decryption) on outbound traffic, you must **exclude Duo's service hosts (`*.duosecurity.com`) from inspection**, otherwise Duo sign-in fails.

## When you need this

Add a certificate when the target server uses:

- a **self-signed certificate**, or
- a certificate issued by an **internal / private certificate authority** that is not publicly trusted.

If you do not add it, the connection fails with an error such as `self-signed certificate in certificate chain`.

## Before you start

- Have the certificate in **PEM** format (a text block beginning with `-----BEGIN CERTIFICATE-----`).
- For a certificate issued by an internal CA, add the **CA certificate** (and any intermediates), not the server's own leaf certificate. Include the full chain when in doubt.

## Add a trusted certificate

1. Open **Settings → Trusted Certificates**.
2. Select **Add certificate**.
3. Enter a **Name** to recognise it later (for example `Internal Mail Relay CA`).
4. Paste the certificate into the text field, or drag and drop a `.pem` / `.crt` file onto the upload area.
5. Select **Add certificate**. The subject, issuer, expiry, and fingerprint are read from the certificate and shown in the list.

You can paste a full chain or bundle (several certificates in one block); each certificate is stored as its own entry.

## Remove a trusted certificate

In the list, select the delete icon on the row and confirm. The certificate is no longer trusted; connections to servers relying on it may then fail.

> **Note:** A change can take a few minutes to apply across all nodes of the instance.

## Reference

| Field | Notes |
|---|---|
| Format | PEM (`-----BEGIN CERTIFICATE-----`). One certificate, a chain, or a bundle. |
| Metadata shown | Name, subject, type (root / intermediate CA or certificate), expiry, fingerprint (SHA-256) |
| Expiry | An expired certificate is rejected on upload; entries close to expiry are flagged in the list |
| Scope | A trusted certificate applies to all outbound TLS connections listed above |

## Troubleshooting

- **`self-signed certificate in certificate chain`**: the server's chain is not fully trusted. Add the issuing CA certificate, including any intermediates and the root.
- **Certificate is expired**: the certificate has passed its validity date. Obtain a current one from the server's operator and add it.
- **Hostname mismatch**: trusting the certificate does not skip hostname verification. The server's certificate must still match the hostname you connect to.
- **Added but the connection still fails**: check that you added the CA certificate (not just the server's leaf certificate) and that the full chain is present.

## See also

- [Email provider](https://dts-identity.com/docs/branding/email.md)
- [Phone / SMS provider](https://dts-identity.com/docs/branding/phone-sms.md)
