stt/kong-customers-api
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: follow the token-exchange broker rename

Browse Source 
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Stéphane Tailland
2026-08-29 07:52:56 +02:00
parent 6c93aec717
commit f0259d8dd9
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+1 -1
View File
@@ -26,7 +26,7 @@ domain needs an MCP entry point.
`openid-connect` on the REST service, `audience_required`/token-exchange `openid-connect` on the REST service, `audience_required`/token-exchange
target = `classic-models-api` (`BACKEND_AUDIENCE`). Unlike `catalog-api`, target = `classic-models-api` (`BACKEND_AUDIENCE`). Unlike `catalog-api`,
there's no MCP hop minting an intermediate `customers-api`-audience token 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 (`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 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 to `classic-models-api` before it reaches the backend, same second-hop