[Improvement]: Retry mechanism for oauth2 upstream-auth policy
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
Gateway
Please select the aspect the issue is related to
Aspect/API (API backends, definitions, contracts, interfaces, OpenAPI)
Suggested Improvement
We need a retry mechanism for the oauth2 upstream-auth policy so that a failed authenticated call to the upstream (e.g. a 401 due to an expired/invalid token) can be retried.
This is applicable to the model failover policy as well. The same problem we have where we need to retry with the fallback model/endpoint when the request fails.
Related Issues
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 locating the oauth2 upstream-auth policy and the model failover policy, then trace how failed authenticated upstream calls are handled. Define the retry and fallback behavior for failures such as expired or invalid tokens, and add tests covering retries and the fallback endpoint or model.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, authentication, backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100