-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Custom Authorizer #66
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This looks great for authorizing with different providers through an intermediary service, and setting up the endpoints to do so!
However, for using the auth-result of this with any other functions, and for re-usability, it seems like an ideal solution would be to use a "custom authorizer" to validate the credentials passed up for subsequent calls which would act as the middleware and pass the profile back to the lambda function.
The test app here appears to put the auth code inline which makes for a lot of duplicate boilerplate.
Authorizer Blueprints: https://github.com/awslabs/aws-apigateway-lambda-authorizer-blueprints/blob/master/blueprints/nodejs/index.js
I'm interested in discussing this, and potentially collaborating on a new project, or helping with this one...
It seems to me that Cognito and Auth0 can be very expensive, and open source Custom Authorizers would be an amazing alternative/cheap open source project to these pay solutions.
Example Deployment:
The text was updated successfully, but these errors were encountered: