Hi,
Have a few queries around Temporal Web UI security as below :
For 1) Temporal web supports OIDC. You can for example set it up via docker env vars
TEMPORAL_AUTH_* key.
Another option is via yaml config, see here.
Will get back to you regarding second question, assuming you are using web ui v2, right?
Ok, will check on point 1. Right now, we are using Web version, but we are open to switch to v2 version. Also, is v2 version published for production setup?
but we are open to switch to v2 version
I think you should consider it. All updates/fixes/new features are going to be added to v2 only from now on. v1 is deprecated in that regard.
v2 dockerhub images (tags): Docker
docker setup example: https://github.com/temporalio/docker-compose/blob/main/docker-compose.yml#L61
helm charts have also been updated to use v2.
is there a provision to enable/disable “Terminate Workflow” button
v1: GitHub - temporalio/web: Temporal Web UI v1 - TEMPORAL_PERMIT_WRITE_API flag
v2: not yet implemented: [0.9.0] Allow disabling write operations · Issue #425 · temporalio/ui · GitHub
But is there no way to set this flag…based on the logged in user?
I don’t think so currently.
Hi,
@tihomir We tried deploying v2 UI using helm chart but facing issue as below when trying to open detailed view of a workflow :
I have 1.14.0 version of temporal server deployed. Please guide.
GetWorkflowExeutionHistoryInReverse api was added in 1.16.0.
Let me check with web team and get back to you on this as it seems 1.16.0 or later is currently a hard requirement.
Yes, there is a requirement for server version 1.16.0 or later, web team updated the readme here as well as docs (pr: here)
Web v2 uses GetWorkflowExeutionHistoryInReverse as it allows reversing workflow history view.
We are discussing this internally and if there is a decision to lift this requirement or a way to maybe bypass this issue will update here.
web team was able to remove this current restriction, see issue here. this should be available in the next ui release.
