Add support for authorizers in websocket APIs
Open
feature-request
- Dominant language
- Python
- Stars
- 11.1k
- Forks
- 1k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
Using @app.router I can define an authorizer field argument to configure authorization layer. In API gateway, I can create a lambda authorizer for $connect, but in @app.on_ws_connect I don't have the authorizer field.
How can I achieve that?
Contributor guide
Research direction
Start by reading the @app.on_ws_connect handler and the @app.router authorizer argument, then compare them with API Gateway WebSocket authorizers for $connect. Define what authorizer information should be available during connection handling and verify the behavior with the relevant WebSocket integration tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- api, authorization, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100