Skip to content

feat(multitenancy): return 404 for unknown tenant on public agent card - #1112

Merged
kabir merged 1 commit into
a2aproject:mainfrom
ehsavoie:issue_1108
Sep 3, 2026
Merged

feat(multitenancy): return 404 for unknown tenant on public agent card#1112
kabir merged 1 commit into
a2aproject:mainfrom
ehsavoie:issue_1108

Conversation

@ehsavoie

Copy link
Copy Markdown
Collaborator

On top of #1111
Fixes #1108 🦕

@ehsavoie ehsavoie changed the title Issue 1108 feat(multitenancy): return 404 for unknown tenant on public agent card Aug 31, 2026
@kabir

kabir commented Sep 2, 2026

Copy link
Copy Markdown
Collaborator

@ehsavoie Needs a rebase

@ehsavoie

ehsavoie commented Sep 2, 2026

Copy link
Copy Markdown
Collaborator Author

@kabir rebased

@ehsavoie
ehsavoie force-pushed the issue_1108 branch 4 times, most recently from 01db8f1 to 6c358af Compare September 3, 2026 10:19
- Add TenantNotFoundException; JSONRPCHandler and RestHandler throw/return 404 when AgentCardRouter is set but tenant not found
- Single-tenant servers (no router) ignore the tenant segment and serve the default card
- CdiAgentCardRouter.resolvePublicCard now returns null for unknown/blank tenants instead of the default card
- Add Utils.buildTenantCardPath helper; restrict fallback retry in A2ACardResolver to 404 only
- Update all tests to expect 404 for unknown tenants

Fixes: a2aproject#1108

Signed-off-by: Emmanuel Hugonnet <ehugonne@redhat.com>
@kabir
kabir merged commit 0b52bf2 into a2aproject:main Sep 3, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: When a tenant doesn't exist, we should return a 404

2 participants