From 6c93aec717bea1398831385ba1b76e801876c51a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?St=C3=A9phane=20Tailland?= Date: Sat, 29 Aug 2026 07:40:06 +0200 Subject: [PATCH] refactor: rename the token-exchange broker to drop the middleware's name Every agent has to name this client in the audience scopes it requests, so the one thing an agent cannot avoid naming was the very thing it should know nothing about. The gateway is replaceable; the contract should not say otherwise. token-exchange-broker, same credential, same behaviour. The old client stays in the realm until every consumer has moved. Co-Authored-By: Claude Opus 5 --- dev/flux-kustomization.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dev/flux-kustomization.yaml b/dev/flux-kustomization.yaml index e2dd304..03f7b8b 100644 --- a/dev/flux-kustomization.yaml +++ b/dev/flux-kustomization.yaml @@ -36,7 +36,7 @@ spec: # record `customers` and turns that into the Loki label domain=customers. AUDIT_LOG_ENDPOINT: http://audit-log-collector.observability.svc.cluster.local/customers REST_HOSTNAME: customers-dev.sttlab.local - TOKEN_EXCHANGE_CLIENT_ID: kong-token-exchange-broker + TOKEN_EXCHANGE_CLIENT_ID: token-exchange-broker # Unused today — same dead variable already present in catalog-api's # flux-kustomization.yaml (kong/mcp/openid-connect.yaml uses # API_AUDIENCE for its audience_required/token_exchange target, not