Provide more context to authorizer functions
Open
feature-request
- Dominant language
- Python
- Stars
- 11.1k
- Forks
- 1k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
The `AuthRequest` instance passed to the authorizer function doesn't provide any context about the request. This makes it impossible to implement rate limiting or blocking IPs that generate too many failed logins. Including the request context would make it possible to implement such protections.
Contributor guide
Research direction
Start by locating the AuthRequest definition and the authorizer invocation path in Chalice. Determine which request context is available there and define how it should be exposed; done means authorizer functions can use that context for protections such as rate limiting or blocking repeated failed logins, with tests covering the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- api, authentication, backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100