fix: Custom Authorizer Lambda Request context missing accountId and apiId fields

[rfranco]

Description

Prior to #1600 change, APIGatewayEvent.requestContext object available in custom authorizer lambda had accountId and apiId fields. We used these fields construct methodArn inside our authorizer lambda. But the above change deleted these fields. Any reason why the fields are removed? AWS Lambda https://github.com/types still refer to these fields.

Fixed: #1635

[closesimple-mf]

Thank you, this fixed our issue so that serverless-offline worked again with our custom authorizer after upgrading.

@dherault could this be merged? This fixes #1475 for us

[nbenoit3]

@dherault Hello, is there any way this PR can be merged in? Currently running into this issue as well.

[dnalborczyk]

thank you @rfranco

[celadari]

Thank you, this fixed our issue so that serverless-offline worked again with our custom authorizer after upgrading.

@dherault could this be merged? This fixes #1475 for us

Hi @closesimple-mf , can you share with me the code that works on your end ?

If I try

return {
            isAuthorized: true,
        };

in my lambda authorizer function I still get the error

Authorization response did not include a principalId

[SeanHaleAtPI]

I am also experiencing the same issue as @celadari . @closesimple-mf WOuld you mind sharing your solution as well?