Temporal UI observes namespaces but does not replace their policy
Temporal coordinates long-running workflows. The Web UI shows workflow executions, event history, and operational state. It is useful for investigating a stuck process, but it is not the enforcement point for every operation. A deployment can expose the UI while the Temporal Service and its namespace policy remain the real authority for clients, workers, and operators.
A count-only ZoomEye query on 2026-11-21 measured app="Temporal" at 197 index matches. title="Temporal" returned 2,181. Both used sub_type=all, page 1, and page size 1. The application field is more specific than the title field, but neither proves that the service is self-hosted, reachable for writes, or unauthenticated. The numbers are inventory observations.
Temporal Cloud documentation separates namespace authentication from Web UI access. A namespace can use API keys or mTLS in Cloud contexts. The Web UI has its own environment variables for frontend connectivity, authentication, TLS, CORS, and codec-server access. The documentation notes that Web UI authentication settings control who can access the UI, not authorization against the Temporal Service. That sentence is the practical boundary.
When reviewing a self-hosted deployment, check three paths separately. First, who can load the UI and read workflow data. Second, which service identity the UI uses when it calls the frontend. Third, which namespace and role the workflow client or worker can use. A UI that requires SSO while its backend client has a broad namespace administrator token is still a powerful observation point.
Namespaces should have ownership and retention rules. A namespace that contains customer workflow history should not share a service account with a development namespace. If a Codec Server is configured, verify whether user access tokens are forwarded to it and whether that server has a scoped identity. A codec endpoint can decode payloads, so it belongs in the data-access review, not only in the UI configuration file.
The network path matters. Keep the UI behind a management network or identity-aware proxy. Restrict the Temporal frontend port to the UI and worker networks. Do not expose the UI's internal service token in browser code. Inventory the TLS server name for each namespace and confirm that certificate validation is enabled on clients.
The candidate count gives an owner a starting population. Reconcile it with DNS and deployment records, then verify the public path with a normal browser request. Do not attempt to read workflow contents, enumerate namespace names, or test worker credentials. A public login page is not proof of a vulnerability; it is evidence that a service surface exists.
Temporal UI helps an operator see workflow state. Namespace authentication and role policy decide what that view can do.
Exact query: app="Temporal"
Open the normalized ZoomEye search
Top comments (0)