Commit Graph

4 Commits

Author SHA1 Message Date
Stéphane Tailland 5b0108fe43 docs: the broker rename is done
The audience table now names token-exchange-broker, and the blocker that
recorded the leak is closed. What remains in that section is the missing
employeeNumber claim, which is unrelated.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-29 07:53:31 +02:00
Stéphane Tailland 3e4e8e363f docs: stop naming the middleware
An agent talks to URLs that honour a contract: an MCP endpoint, an OIDC token
endpoint, an OpenAI-shaped LLM endpoint. Whatever serves those URLs is
replaceable, and naming it in an agent's code or docs implies a coupling that
does not exist.

Every product name is gone from prose, comments and identifiers, replaced by
what the agent actually depends on. Where a behaviour of the current middleware
leaks into the contract — the second audience scope, the tool ACL — the text
now says what the caller must do and why, not who imposes it.

One string survives and cannot be fixed here: the broker client an agent must
name in its audience scopes is itself named after the middleware. Closing that
means renaming it in Keycloak and following the rename through the gateway
configuration and LibreChat. Recorded as a blocker.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-29 07:35:13 +02:00
Stéphane Tailland 92f0a272a5 docs: correct the audience table and refresh the blockers
- Two audience scopes per MCP server, not one: Kong's own openid-connect
  plugin re-exchanges the token, so it must also name
  kong-token-exchange-broker. Measured on catalog.
- Drop the resolved Konnect-not-persisting blocker; the cause was a dead
  Konnect org, not Konnect refusing writes.
- Drop the resolved kong-token-exchange-broker secret mismatch; its
  client_credentials returns 200.
- Record the real blocker: PydanticAI's MCP client cannot open a session
  against ai-mcp-proxy.
- Document the realm's override-on-start import and ${KC_SECRET_*}
  placeholders, and the a2a-sdk 1.x serving requirements.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-28 10:36:47 +02:00
Stéphane Tailland ddc0f24cb9 Add implementation instructions
Design agreed in discussion, nothing built yet. Records the agent's role, its
scopes and MCP servers, its A2A surface, and the framework choice with its
reason — so the next session starts from the decisions rather than re-deriving
them.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-26 15:14:41 +02:00