-
Notifications
You must be signed in to change notification settings - Fork 14
Lamdba Authorizers #407
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
base: master
Are you sure you want to change the base?
Lamdba Authorizers #407
Conversation
✅ Deploy Preview for gracious-clarke-e6b312 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please also add the cover image (of two different sizes) and the metadata
|
||
JWTs (JSON Web Tokens) have become the go-to standard for API authentication, and for good reason. They’re lightweight, secure, and perfect for modern, distributed systems. When paired with **Lambda Authorizers**, JWTs provide a robust way to authenticate and authorize API requests. Let’s break it down. | ||
|
||
### **Why JWT?** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is a little repetition, there is another instance above where we are explaining what JWTs and the claims are. It should be consolidated into a single place
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, working on it.
Related Issue
Link to the Github Issue created for this blog post
Link to Google Doc
https://docs.google.com/document/d/1AG6IMoqkCTSRCCStmOIldMF5610D3_d-c2YRUZH_75k/edit?tab=t.0
Checklist
Remaining TODOs