> For the complete documentation index, see [llms.txt](https://wiki.datadike.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.datadike.com/pam/deploy-operate/certificates.md).

# Certificates and HTTPS

Serving the console over HTTPS: the name the certificate has to match, the Site URL setting that has to agree with it, and what breaks quietly when the two disagree.

## What this is and when to use it

Two separate things have to line up before the console is properly served over HTTPS, and confusing them is the reason this page exists:

* **The certificate** that terminates HTTPS for web access, installed on the server and matching the DNS name your users type.
* **Site URL**, a setting that tells the solution its own public address.

The certificate makes the browser stop warning. Site URL is what the solution puts into notification email links, SSO redirects and internal callbacks. Getting the certificate right and leaving Site URL alone produces an installation that looks finished — the login page loads over HTTPS with no warning — and quietly breaks single sign-on and every link the system sends by email.

Certificates elsewhere in the product are different trust chains and are not configured here: LDAPS uses its own certificate files loaded on the appliance, the broker authenticates gateways and connectors with its own PKI, and SMTP TLS is configured with the mail server. Fixing the console certificate does not touch any of them.

{% hint style="warning" %}
**Installing the certificate is not a self-service step.** DataDike implementation support imports your wildcard on the server by command line. A Settings screen for uploading a wildcard or subdomain certificate also exists; which of the two paths applies depends on your installation and version, and support will confirm it.
{% endhint %}

## What is established

| Fact                                                                         | Note                                                                                                                                       |
| ---------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| The web interface is served over HTTPS for browser access                    | Stated as a platform characteristic                                                                                                        |
| Either your own certificate or automatic issuance can be used for web access | Which of the two applies to your installation and version has to be confirmed with support; the source states no more than that both exist |
| The certificate is imported on the server by implementation support          | Stated for the wildcard case                                                                                                               |
| The address must be a DNS name that resolves for your users                  | A certificate matches names, and the temporary setup path uses a hosts-file entry that only exists on one machine                          |

## Before you start

* **Settle the DNS name first.** The certificate matches the name users type, Site URL is built from it, and changing it later means revisiting both.
* **Have the certificate.** A wildcard or a subdomain certificate covering that name.
* **Know your two DNS stages.** The source describes the setup deliberately in two: a **temporary** stage, where you add a hosts-file entry on your own machine purely to reach the appliance during setup, and the **definitive** stage, where records exist in your private DNS — plus your public DNS, if you publish the console to the internet through NAT/DNAT. The hosts entry is scaffolding; leaving it in place is how one administrator ends up seeing a working system nobody else can reach.
* **Engage implementation support** for the import.

## Steps

1. **Fix the hostname and create the definitive DNS records** for the name the certificate covers — private DNS, and public DNS as well if the console is published externally.
2. **Have support import the certificate** on the server.
3. **Set Site URL** under **System Settings › General › Basic** to the full URL of that name, with the `https://` scheme and **no trailing slash**.
4. **Restart the dependent components** after changing Site URL. The source is explicit that the change needs this to be applied.
5. **Remove the temporary hosts-file entry** from your own machine, so that you are testing what everyone else sees.

## What Site URL is used for

This is why step 3 is not cosmetic. Site URL is consumed internally by:

| Consumer                                                                | Effect of a wrong value                                               |
| ----------------------------------------------------------------------- | --------------------------------------------------------------------- |
| Links in notification email — alerts, access approvals, password resets | Recipients get a link to the old address, or to an IP over plain HTTP |
| Redirects after SSO authentication (SAML2, OIDC, OAuth2)                | Federated login fails or loops, while local login keeps working       |
| Internally generated callbacks and webhooks                             | Integrations fail to call back                                        |
| Remote access client download, where configured                         | Clients download from an address that may not resolve for the user    |

It is required, and it must be reachable from the clients that use the platform — not merely resolvable on the server.

## How to verify it worked

Each check below exercises a different consumer of the configuration, because the browser padlock only proves the first one.

1. **Open the console by the exact DNS name over HTTPS**, from a machine with no hosts-file entry. No warning, and the certificate's name matches the name in the address bar.
2. **Fetch the unauthenticated health endpoint over HTTPS on that same name**: `/api/health/` should return its JSON. This confirms TLS terminates on the name and the application answers behind it, which a static error or maintenance page would not.
3. **Trigger something that sends a link** — a notification email you can receive — and confirm the link uses the HTTPS name rather than an IP or `http://`. This is the check for Site URL, and nothing about the browser view substitutes for it.
4. **Perform one login through your identity provider.** The post-authentication redirect has to land on the HTTPS name. A stale Site URL breaks exactly this while leaving local login healthy, so testing with the local admin account proves nothing here.
5. **If a vulnerability scanner or other integration consumes the credential API**, confirm its connector still works: it requires the HTTPS base URL and a certificate its own trust store accepts. An internal CA that browsers trust because of a group policy is not necessarily trusted by a scanner appliance.

{% hint style="warning" %}
**Nothing in the source documents an expiry alert for the console certificate.** Track the expiry date outside the product — in your certificate inventory or your monitoring system. A certificate that expires takes browser access down for everyone at once, and it does so on a date that was known months in advance.
{% endhint %}

## Common errors

| Symptom                                                                     | Cause                                                                                                                                | Fix                                                                                                         |
| --------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------- |
| Console loads over HTTPS, but SSO login loops or lands on the wrong address | Site URL was not updated to the HTTPS name                                                                                           | Set Site URL under **General › Basic**, then restart the dependent components                               |
| Email links point at an IP address or `http://`                             | Site URL still holds its setup-time value                                                                                            | Same fix. Verify by receiving an email, not by re-reading the field                                         |
| Certificate warning in the browser after the install                        | The name being typed is not covered by the certificate, or DNS still resolves through a leftover hosts entry                         | Use the name the certificate covers; remove hosts-file entries and confirm the definitive DNS records exist |
| Works for the administrator, unreachable for everyone else                  | The temporary hosts-file entry is still doing the resolution on that one machine                                                     | Create the definitive private DNS records, and public records if the console is published                   |
| A scanner or A2A integration cannot connect                                 | Base URL without HTTPS, or a certificate the integration does not trust                                                              | Use the HTTPS base URL and make the certificate trusted by that client                                      |
| LDAPS still fails after the console certificate is fixed                    | LDAP TLS uses its own files — `ldap_ca.pem`, `ldap_cert.pem`, `ldap_cert.key` — loaded on the appliance, and needs a service restart | Handle the LDAP certificates separately from the console certificate                                        |
| Gateway connections fail after moving to a release that enforces TLS 1.3    | 5.0.1 enforces TLS 1.3 between the Gateway VM and the server, and its release note states a restart is required                      | See [Upgrade](https://wiki.datadike.com/pam/deploy-operate/upgrade.md)                                      |
| Broker enrolments break after changing the broker's address                 | The broker's address is written into its certificates and enrolment tokens and cannot be changed afterwards                          | Always address the broker by DNS name; changing it otherwise means reinstalling the broker                  |

## Related pages

* [Upgrade](https://wiki.datadike.com/pam/deploy-operate/upgrade.md)
* [Monitoring and health](https://wiki.datadike.com/pam/deploy-operate/monitoring.md)
* [Ports](https://wiki.datadike.com/pam/reference/ports.md)
* [Core concepts](https://wiki.datadike.com/pam/get-started/core-concepts.md)
