WebSocket Authorization Request Context need to be sended to all routes #1379
Comments
brazilianbytes
added a commit
to brazilianbytes/serverless-offline
that referenced
this issue
Apr 26, 2022
brazilianbytes
added a commit
to brazilianbytes/serverless-offline
that referenced
this issue
May 5, 2022
|
fixed with: #1380 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Current Behavior
When you use a WebSocket Lambda Custom Authorizator and this result is 'allow', all socket messages has the requestContext with the Authorization object. This is actually sent with the $connect route only.
Expected behavior/code
The requestContext need to be present on all routes, like the API Gateway behavior.
Environment
serverlessversion: [3.14.0]serverless-offlineversion: [8.7.0]node.jsversion: [e.g. v14.9.0]OS: [Ubuntu 21.10]Possible Solution
I will open a pull request with the code fix.
The text was updated successfully, but these errors were encountered: