[Task]: Secrets GW integration tests are not actually validating Upstream.Auth of LLM Providers
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
Area/Gateway (Routing, API deployment in gateway etc.)
Please select the aspect the issue is related to
Aspect/API (API backends, definitions, contracts, interfaces, OpenAPI)
Description
Here we are configuring Upstream Auth, but this Auth header is not actually validating (from the mock service or from the test itself). Hence, this is not actually testing secrets with LLM providers.
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
Inspect gateway/it/features/secrets.feature around lines 369-372 and the mock service or test setup referenced there. Make the integration test genuinely validate the configured Upstream.Auth header for the LLM provider, then run the relevant Secrets Gateway integration test. Done means incorrect or missing upstream authentication causes the test to fail.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, security, testing-qa
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100