[Bug]: LLM Provider "Models" tab access control is not enforced at the gateway
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 71
- Forks
- 111
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 110
Description
Please select the area the issue is related to
AI Workspace
Please select the aspect the issue is related to
Aspect/API (API backends, definitions, contracts, interfaces, OpenAPI)
Description
The Models tab in AI Workspace is documented to block access to any model that is disabled or not present in the "Models Available" list . Even without adding a model to the Models tab for a specific provider, it can still be used through the gateway. Also tried adding a model and then removing it from the list even then, it can still be used. The Models tab does not appear to restrict access at the gateway as expected.
Steps to Reproduce
- Create an LLM provider (e.g. Gemini) in AI Workspace.
- Go to the Models tab and note a model that is NOT in "Models Available" (or remove one that is), then Deploy.
- Invoke a request related to that model.
- Observe the request succeeds with a normal upstream response, instead of being blocked.
Severity Level of the Issue
Severity/Blocker (Core functionality is broken and consumer is blocked. Need immediate attention)
Environment Details (with versions)
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the request through the gateway after deploying an AI Workspace provider with a model absent from, or removed from, the Models Available list. Trace the gateway entry point for provider model requests and compare allowed and disallowed models. Done means disabled or unlisted models are blocked while permitted models continue to receive normal upstream responses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ai, api, authorization, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100