From 74960dc444f09d32153e10899bc5a50a920a6d8d Mon Sep 17 00:00:00 2001 From: Manish Kumar Date: Tue, 4 Aug 2026 00:28:27 -0500 Subject: [PATCH] chore: wire JWT_SECRET into tes service (TES IAM integration dependency) TES's authentication now goes through omnibioai-iam-client (see omnibioai-tes's TES IAM integration PR), which needs JWT_SECRET for its HS256 fallback verification path -- same var name/value every other JWT_SECRET consumer in this file already uses. IAM_URL/REDIS_URL were already wired for tes. --- docker-compose.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docker-compose.yml b/docker-compose.yml index 14034ef..9532345 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -69,6 +69,10 @@ services: TES_SERVERS: /workspace/configs/servers TMPDIR: /tmp/omnibioai_tes_runs IAM_URL: http://auth-service:8001 + # TES IAM integration: HS256 fallback secret for the shared IAM + # client's local decode -- same var name/value already wired into + # every other JWT_SECRET consumer in this file. + JWT_SECRET: ${AUTH_SECRET_KEY:-change-me} POLICY_URL: http://policy-engine:8002 HPC_POLICY_URL: http://hpc-policy-engine:8003 AUDIT_URL: http://security-audit:8004