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 <noreply@anthropic.com>
This commit is contained in:
Stéphane Tailland
2026-08-29 07:40:06 +02:00
parent df25247f22
commit 6c93aec717
+1 -1
View File
@@ -36,7 +36,7 @@ spec:
# record `customers` and turns that into the Loki label domain=customers. # record `customers` and turns that into the Loki label domain=customers.
AUDIT_LOG_ENDPOINT: http://audit-log-collector.observability.svc.cluster.local/customers AUDIT_LOG_ENDPOINT: http://audit-log-collector.observability.svc.cluster.local/customers
REST_HOSTNAME: customers-dev.sttlab.local 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 # Unused today — same dead variable already present in catalog-api's
# flux-kustomization.yaml (kong/mcp/openid-connect.yaml uses # flux-kustomization.yaml (kong/mcp/openid-connect.yaml uses
# API_AUDIENCE for its audience_required/token_exchange target, not # API_AUDIENCE for its audience_required/token_exchange target, not