Open kevinhankens opened 1 year ago
Greetings! Any chance of taking a look at this and the accompanying PR? We currently have to use a odd workflow to patch this for local development. Would be really helpful to get some movement on this. Thanks in advance!
Hello again 😉 Kindly asking for assistance with this one.
Amazing Work @kevinhankens! Thanks for fixing this.
I think this issue should be closed now. For someone who has this issue in serverless offline: You could fix this problem in a tricky way like adding the isOffline variable to your environment and passing only one header to identifysource.
identitySource: conf(GlobalConfig, 'IS_OFFLINE', false)
? 'method.request.header.x-api-key'
: 'method.request.header.x-api-key, method.request.header.x-secret-key',
Bug Report
Greetings! I have found that when validating REST API authorizers it only allows for one identitySource header. For caching, multiple headers are allowed.
According to the REST API docs:
Current Behavior
Using something like the following will fail to start:
Errors with:
Sample Code
Here's a link to the code
Expected behavior/code
The above example should start offline.
Environment
serverless
version: 3.28.1serverless-offline
version: 12.0.4Possible Solution
Additional context/Screenshots