Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Custom authorizer - Does not get triggered

See original GitHub issue

I am using a custom authorize lambda function with Node to authenticate the apis, after deploying i can manually test authorize function and it logs the errors in cloud watch. But when i request the same api through postman, it does not log anything on the cloud watch. It always returns the error 401 unauthorized.

Here is the code:

functions:
 testAuthorize:
    handler: handler.testAuthorize
accountFunctions:
    handler: handler.accountFunctions
    events:
      - http:
            path: account/testApi
            method : get
            authorizer: testAuthorize

Issue Analytics

State:
Created 6 years ago
Comments:13 (6 by maintainers)

Top GitHub Comments

2reactions

sajeetharancommented, Jun 23, 2017

Sorry guys, i had to add the custom headers in the cloud front distribution to get it worked . thanks @HyperBrain and @pmuens cheers!

1reaction

pmuenscommented, Jun 23, 2017

Sorry guys, i had to add the custom headers in the cloud front distribution to get it worked . thanks @HyperBrain and @pmuens cheers!

Great! Thanks for adding a comment which explains how you were able to resolve it 👍 !

Glad to hear that it’s working for you now.

Top Results From Across the Web

AWS API Gateway Custom Authorizer not invoked

After adding variables to the deployment to trigger a redeployment, the custom authenticater was properly called as expected.

Custom Authorizer not being triggered - Serverless Framework

I am trying to implement a custom authorizer for my functions triggered via API Gateway (http event). However, it looks like the authorizer ......

Custom authorizer does not get triggered after deployment

Everything has been working just fine except that after re-deployment at times, the custom authorizer won't get triggered at all before ...

Troubleshooting your authorizers - AWS IoT Core

Malformed connection requests can cause AWS IoT Core not to trigger your authorizer. Connection problems can occur at both the TLS and application...

Websockets Authorizer function is not triggered by Querystring ...

According to your screenshot, you didn't change the identity source but you added additional identity source. Unless the request has both header and...