Native SSL/TLS Support for Pulse Web UI

This document explains how to enable SSL/TLS support for Pulse Web UI without using an ad-proxy (Traefik) container.

Configuration Steps

Generate ad-core Services Configuration (if not available)

Check whether the ad-core services configuration file exists by running the following command.

Bash
Copy
  • If the file exists, proceed to Step 2 with editing the file.
  • If it does not exist, generate it using the command below:
Bash
Copy

Edit the ad-core.yml File

After the configuration file is generated, open the file in an editor. Locate the ad-graphql section and find the environment subsection as shown in the example below.

Update the SSL configuration variables as needed. For details about the configurations, see SSL Configuration Options.

Bash
Copy

Restart the ad-graphql Service

Restart the ad-graphql service using the following command:

Bash
Copy

Verify the Service Status

Check for any errors in the ad-graphql service container logs:

Bash
Copy

If no errors are visible, the service has successfully launched.

Access the Pulse Web UI

Once the configuration is complete, access the Pulse Web UI using the HTTPS protocol in your browser:

Bash
Copy

If configured correctly, Pulse will now serve the UI securely over HTTPS.

SSL Configuration Options

Variable NameDefault ValueMandatory?Description
MONGO URI-YesConnection string for the MongoDB instance used by Pulse.
MONGO_ENCRYPTEDTrueYesEnables or disables encryption for MongoDB credentials. Set to true to store the Mongo URI in encrypted form.
MONGO_SECRET-YesSecret key used for decrypting the MongoDB connection string.
UI_PORT4001YesDefines the HTTP and HTTPS ports for the Pulse Web UI.
LDAP_PORT19020YesPort number used by the LDAP service for authentication.
SSL_ENFORCEDTrueYesEnforces HTTPS for the UI port inside the container. This disables the HTTP port.
SSL_ENABLEDFalseYesEnables HTTPS for the UI port inside the container, while keeping the HTTP port active.
SSL_KEYDIR/etc/acceldata/ssl/YesThe directory inside the container where the SSL/TLS key file is located.
SSL_KEYFILEssl.keyYesName of the SSL/TLS key file inside the container.
SSL_CERTDIR/etc/acceldata/ssl/Yes

The directory inside the container where the SSL/TLS certificate file is located.

The certificate directory must be accessible to the Pulse container user (user-id: 1000).

SSL_CERTFILEssl.crtYesName of the SSL/TLS certificate file inside the container.
SSL_PASSPHRASEOptionalSpecifies the passphrase required to unlock the SSL/TLS private key file, if the key is password-protected.
SSL_UI_PORT4000YesSpecifies the HTTPS port for accessing the Pulse Web UI.
DS_HOSTad-query-estimationYesHostname of the query estimation service used by Pulse.
OTEL_JAVAAGENT_ENABLEDfalseYesEnables or disables OpenTelemetry Java Agent for distributed tracing.
DS PORT8181YesPort number for the data service (query estimation) that Pulse communicates with.
ES USERNAME-YesUsername for connecting to the Elasticsearch service.
ES PASSWORD-YesPassword for authenticating with the Elasticsearch service.

For details on updating and using the SSL options, see Update the SSL Options for UI.

Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard