From f0259d8dd9253f89d49128722728a6e512a708aa Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?St=C3=A9phane=20Tailland?= Date: Sat, 29 Aug 2026 07:52:56 +0200 Subject: [PATCH] docs: follow the token-exchange broker rename Co-Authored-By: Claude Opus 5 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 1ed70ee..b5a6e13 100644 --- a/README.md +++ b/README.md @@ -26,7 +26,7 @@ domain needs an MCP entry point. `openid-connect` on the REST service, `audience_required`/token-exchange target = `classic-models-api` (`BACKEND_AUDIENCE`). Unlike `catalog-api`, there's no MCP hop minting an intermediate `customers-api`-audience token -today — a caller gets one directly via `kong-token-exchange-broker` +today — a caller gets one directly via `token-exchange-broker` (`customers-api-audience` client scope, added there 2026-08-23) and calls these routes with it; the REST-layer plugin then exchanges that token again to `classic-models-api` before it reaches the backend, same second-hop