From dcc93f0f68994e9ad24e12a67e93c9e8d5d062b3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?St=C3=A9phane=20Tailland?= Date: Sat, 29 Aug 2026 07:40:03 +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 5de14f7..7489dd5 100644 --- a/dev/flux-kustomization.yaml +++ b/dev/flux-kustomization.yaml @@ -33,7 +33,7 @@ spec: AUDIT_LOG_ENDPOINT: http://audit-log-collector.observability.svc.cluster.local/catalog REST_HOSTNAME: catalog-dev.sttlab.local MCP_AUDIENCE: '["mcp-catalog"]' - TOKEN_EXCHANGE_CLIENT_ID: kong-token-exchange-broker + TOKEN_EXCHANGE_CLIENT_ID: token-exchange-broker substituteFrom: - kind: Secret name: catalog-token-exchange-broker