-
Notifications
You must be signed in to change notification settings - Fork 177
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
Add support for providing a function as the key #22
Comments
oh, that's a good idea.
yes, a kid validation function sounds good. |
OK - I'll get it worked up probably tomorrow and get something submitted for review. |
toonetown
added a commit
to toonetown/lua-resty-jwt
that referenced
this issue
Apr 20, 2016
This fixes SkyLothar#22. It also updates the documentation and adds unit tests surrounding the feature.
SkyLothar
pushed a commit
that referenced
this issue
Apr 21, 2016
This fixes #22. It also updates the documentation and adds unit tests surrounding the feature.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be helpful to be able to provide a function or a string as the key to the verify functions. Such a function would be passed the value of
kid
from the header as a single parameter, and would return a string to use as the key. This would simplify, for example, using a hash table or a Redis database for looking up keys based off of thekid
parameter.I actually have some code that does this, and am willing to put together a pull request if it would be something that is desired.
The text was updated successfully, but these errors were encountered: