This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of koa-jwt.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Add the ability to pass a function to opts.secret. This function is provided with the decoded header from the JWT. It should return a promise that resolves to the secret to use for verification of the token.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Hello lovely humans,
koa-jwt just published its new version 3.1.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of koa-jwt. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
GitHub Release
Add the ability to pass a function to
opts.secret
. This function is provided with the decoded header from the JWT. It should return a promise that resolves to the secret to use for verification of the token.The intended use case for this is to allow the use of JWKS via https://github.com/auth0/node-jwks-rsa.
Thanks to @dunnock for the PR.
The new version differs by 91 commits (ahead by 91, behind by 27).
a19d21f
add @dunnock to list oc contributors
d63f949
3.1.0
d04582c
Merge branch 'koa-v2' of github.com:koajs/jwt into koa-v2
7bf9bb8
Merge pull request #90 from dunnock/koa-v2
4f88cf2
fixes for readme per PR #90
c102997
fixes for readme per PR #90
eac4acd
fixes for readme per PR #90
62ecd99
fixes for readme per PR #90
a9d300a
fixes for readme per #90
f3ccb01
fixes for PR #90
a2c6bfa
add missing tests per PR #90
c2ec11b
get rid of isFunction check
fd5d227
fix docs to the new jwks promise provider
92be78a
code review fixes #90
c22816d
fixed error handler for rsa callabck
There are 91 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.