Skip to main content

Temporal Web UI environment variables reference

You can use environment variables to dynamically alter the configuration of your Temporal Web UI.

These can be used in many environments such as Docker. For example:

The environment variables are defined in the UI server configuration template file and described in more detail below.


The Frontend Service address for the Temporal Cluster. This environmental variable can be set in the base configuration file using temporalGrpcAddress.

This variable is required for setting other environmental variables.


The port used by the Temporal WebUI Server and the HTTP API.

This variable is needed for TEMPORAL_OPENAPI_ENABLED and all auth-related settings to work properly.


Stores a value such as "" or "/custom-path" that allows the UI to be served from a subpath.


Enables or disables Web UI authentication and authorization methods.

When enabled, the Web UI will use the provider information in the UI configuration file to verify the identity of users.

All auth-related variables can be defined when TEMPORAL_AUTH_ENABLED is set to "true". Disabling the variable will retain given values.


The .well-known IDP discovery URL for authentication and authorization.

This can be set as in the UI server configuration with auth.


The URL for the authentication or authorization issuer.

This value is only needed when the issuer differes from the auth provider URL.


The client ID used for authentication or authorization.

This value is a required parameter.


The client secret used for authentication and authorization.

Client Secrets are used by the oAuth Client for authentication.


The callback URL used by Temporal for authentication and authorization.

Callback URLs are invoked by IDP after user has finished authenticating in IDP.


Enables or disables the browser UI for the Temporal Cluster.

Enabling the browser UI allows the Server to be accessed from your web browser. If disabled, the server cannot be viewed on the web, but the UI server APIs remain available for use.


Enables or disables OpenAPI features for the Temporal Web UI.

This can be set initially with the enableOpenAPI UI configuration. The documentation can be found at /openapi/ on your Temporal Cluster.

This variable requires TEMPORAL_UI_ENABLED to be set to 'true'.


The default Namespace that the Web UI opens first.


The URL that users are directed to when they click the Feedback button in the UI.

If not specified, this variable defaults to the UI's GitHub Issue page.


Enables or disables notifications that appear in the UI whenever a newer version of the Temporal Cluster is available.


Determines how often the UI Server reads the configuration file for new values.


The path for the Transport Layer Security (TLS) Certificate Authority file.

In order to configure TLS for your server, you'll need a CA certificate issued by a trusted Certificate Authority. Set this variable to properly locate and use the file.


The path for the Transport Layer Security (TLS) Certificate.

In order to configure TLS for your server, you'll need a self-signed certificate. Set the path to allow the environment to locate and use the certificate.


The path for the Transport Layer Security (TLS) key file.

A key file is used to create private and public keys for encryption and signing. Together, these keys are used to create certificates.


Stores the data for a TLS CA file.

This variable can be used instead of providing a path for TEMPORAL_TLS_CA.


Stores the data for a TLS cert file.

This variable can be used instead of providing a path for TEMPORAL_TLS_CERT.


Stores the data for a TLS key file.

This variable can be used instead of providing a path for TEMPORAL_TLS_KEY.


Enables or disables Transport Layer Security (TLS) host verification.

When enabled, TLS checks the Host Server to ensure that files are being sent to and from the correct URL.


The server on which to operate Transport Layer Security (TLS) protocols.

TLS allows the current server to transmit encrypted files to other URLs without having to reveal itself. Because of this, TLS operates a go-between server.


The endpoint for the Codec Server, if configured.


Whether to send a JWT access token as ‘authorization' header in requests with the Codec Server.


Forward-specified HTTP headers to direct from HTTP API requests to the Temporal gRPC backend.


Disables any button in the UI that allows the user to modify Workflows or Activities.