-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Support for Asymmetric (Public Key) JWT Validation #22
Comments
@cancan101 Thank you. Your input has been especially helpful. I'm publishing a JAWS Road Map this weekend. This will be in there. |
Update 8/13/15: We’re currently working on a document that outlines the specifications for JAWS v1.0.0. A proposed resolution to this issue in particular is included in that document. Today or tomorrow, we will share the document for everyone to comment on because your feedback is essential. |
Hey @ac360 I noticed that you removed this from the v1.0 milestone. Does that mean integrated JWT support won't be coming any time soon? |
@AnalogJ going forward you do not have to rely on the serverless middleware and could use any JWT compatible library or tooling for your lambda functions. We are looking into potential authentication in our future SDK, but don't have specific plans yet. For the time I'll close this issue as we will be tracking this separately if we plan to integrate this directly into serverless, but you can absolutely use JWT already in your V1.0 lambdas. |
Modify this to support alternative validation schemes: https://github.com/auth0/node-jsonwebtoken#jwtverifytoken-secretorpublickey-options-callback.
The text was updated successfully, but these errors were encountered: