Update hapi-auth-jwt2 to version 7.1.2 🚀 #52
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello lovely humans,
hapi-auth-jwt2 just published its new version 7.1.2.
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 hapi-auth-jwt2.
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 ✨
You rock!
🌴
The new version differs by 13 commits .
5145c41
default to decoded when credentials are not returned by verifyFunc() callback. 100% backward compatible. fixes verifyFunc() callback
credentials
arg isn't optional as expected dwyl/hapi-auth-jwt2#187 - as documented alreadyfdcbb76
ensure that credentials argument is not required in verifyFunc() callback as documented. default to
decoded
when not supplied. fixes verifyFunc() callbackcredentials
arg isn't optional as expected dwyl/hapi-auth-jwt2#18748024e1
tidy up module and docs (add to FAQ) in response to issues raised. 100% backward compatible
4190f0e
merge master into tidy-up branch
1a2c9a5
tidy up module and docs (add to FAQ) in response to issues raised. 100% backward compatible
dc888bf
Document availability of request.auth.token in verifyFunc() closes Document availability of request.auth.token in verifyFunc() dwyl/hapi-auth-jwt2#184
3a1fe06
remove the
hard-coding of the word
Token` from all boom (raiseError) calls. fixes Hard-codedToken
auth-scheme inWWW-Authenticate
challenge dwyl/hapi-auth-jwt2#18000b92b3
adds FAQ answer for question of Redirecting when Auth fails (e.g. token expired) closes How do you redirect if a token has expired? dwyl/hapi-auth-jwt2#161
486c61e
adds answer to FAQ question about setting JWT auth for all routes asked by @abeninskibede in Q: How do I set jwt auth to all routes? dwyl/hapi-auth-jwt2#149 closes #149
39af1f0
adds answer to FAQ on invaldating tokens. see: question. How do I invalidate an existing token? dwyl/hapi-auth-jwt2#126 closes #126
78fee8c
update readme > FAQ with link to @avanslaars Glue usage example: Integration with glue dwyl/hapi-auth-jwt2#151 (comment) closes #151
721f8f2
update versions of dependencies & devDependencies to latest. no change required to any code. 100% backward compatible
68b9db0
re-name tests to match test/*.test.js (consistency)
See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade