-
Notifications
You must be signed in to change notification settings - Fork 407
(chore): Add JWT Decoder and Signature Verifier #1204
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
Conversation
lahirumaramba
commented
Mar 21, 2021
- Refactoring verify token take 2
- Add JWT Decoder class
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.
I think this needs a bit more work in terms of getting the abstractions right. I've proposed some ideas. PTAL.
0093f57 to
e118e6a
Compare
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.
Overall approach and design is correct. I found a bunch of nits that can be cleaned up. I haven't looked at all the error handling bits yet. I'll get to that in the next round.
83852f5 to
5a1b28c
Compare
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.
Thanks for addressing all the feedback. Looks pretty good! Few more things to revise and we are good to go.
src/auth/token-verifier.ts
Outdated
| const publicKeysStillValid = (publicKeysExpiredExists && Date.now() < this.publicKeysExpireAt); | ||
| if (publicKeysExist && publicKeysStillValid) { | ||
| return Promise.resolve(this.publicKeys); | ||
| if (!(error instanceof JwtError)) { |
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.
Just curious as to what other error conditions can pop up here. Can we guarantee that this API only ever sees JwtError instances?
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.
We throw HttpError from KeyFetcher (if the fetcher is used directly without the getKey callback) and Error types for value errors.
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.
Since we don't call that API directly, I think that case can never occur right? We will only see JwtError here.
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.
Thank you for the feedback!!
Updated the PR.
I removed the algorithm parameter from the API and updated the unit tests to reflect that change.
I will follow up with another update to add unit tests for the new components. Thanks!
src/auth/token-verifier.ts
Outdated
| const publicKeysStillValid = (publicKeysExpiredExists && Date.now() < this.publicKeysExpireAt); | ||
| if (publicKeysExist && publicKeysStillValid) { | ||
| return Promise.resolve(this.publicKeys); | ||
| if (!(error instanceof JwtError)) { |
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.
We throw HttpError from KeyFetcher (if the fetcher is used directly without the getKey callback) and Error types for value errors.
656276d to
8848ac6
Compare
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.
I'm at an LGTM with a few open comments/suggestions.
src/auth/token-verifier.ts
Outdated
| const publicKeysStillValid = (publicKeysExpiredExists && Date.now() < this.publicKeysExpireAt); | ||
| if (publicKeysExist && publicKeysStillValid) { | ||
| return Promise.resolve(this.publicKeys); | ||
| if (!(error instanceof JwtError)) { |
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.
Since we don't call that API directly, I think that case can never occur right? We will only see JwtError here.
05e56e4 to
752de13
Compare