Repository navigation
Per-API-key account pinning (choose which provider accounts each key can use) #5645
fariaotavio12
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Summary
Per-key access control (v0.5.119) already lets me restrict an API key to specific combos/models. What's still global is which account serves the request: with several accounts of the same provider, selection is fill-first/round-robin across all of them, no matter which key is calling.
I'd like to pin an API key to specific connected accounts per provider.
Motivation
I run several tools/projects against one 9router instance and need to separate them:
Today the only way is one 9router instance per use case.
Proposal (implemented in #5642)
access.connections = { providerId: connectionId[] }, set throughPUT /api/keys/[id].I'm already running it on my own instance and verified both paths against the built image: a key pinned to a real account is served by that account, and a key pinned to a missing account gets a clear 404 instead of falling back to another one.
Questions
All reactions