-
Notifications
You must be signed in to change notification settings - Fork 338
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
feat: jwt-validator example #1218
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
f4ffeb9
to
2018249
Compare
19a4558
to
f6f8ec4
Compare
f6f8ec4
to
93f2af6
Compare
I think we can land this, but we're missing an end 2 end test to ensure this has CI coverage and allows for regression testing. This is important so that if we make a change to the API, we can ensure that this test will be updated when the tests break. |
I suggest we make |
Adds a JSON Web Token validator to demonstrate validating RS256 signed tokens in the guest. --------- Co-authored-by: Frank Laub <flaub@risc0.com>
Adds a JSON Web Token validator to demonstrate validating RS256 signed tokens in the guest. --------- Co-authored-by: Frank Laub <flaub@risc0.com>
Move jwt validation to main function call for e2e testing. In reference to this: #1218 (comment) Note: jwt example e2e tests have a large cycle count --------- Co-authored-by: Erik Kaneda <erik@risczero.com>
Adds a JSON Web Token validator to demonstrate validating RS256 signed tokens in the guest.