-
Notifications
You must be signed in to change notification settings - Fork 126
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
Using JWT via URI #19
Comments
Hi @carlskii |
@carlskii What would you want to call the URL parameter? |
@carlskii we can implement this in no time. please just let us know what url parameter you want to use. thanks. |
I guess it could just be called "token". The use case for me would be to ideally generate a time expiring key or token to some of my routes. A bit like Amazons S3 signed url feature. Not sure though if JWT is the right thing for this though. |
Using the exp (expiry) time stamp in the JWT you can easily reject a token that has expired. |
Yes that's the plan. Sent from my iPad
|
Ok, do you have time to help us write some code or documentation for the feature? (If you're low on time we could squeeze it in tomorrow and send you a pull request for review...) |
I can help document it, but my skills with regards writing the code for this type of thing are limited. Sent from my iPad
|
What is the status on this issue? Is this project maintained (no reply since April 22 on the issue)? |
@rainabba thanks for reminding us about this! This module is maintained and actively used. |
@carlskii we have released |
Much appreciated! |
@rainabba we appreciate you keeping us on our toes! 😉 |
Just needed this feature, thanks feature requesters of times past! |
@alexdrans yeah, we're lucky that way...! ❤️ |
Hi,
I need to configure HAPI to accept the JWT via the URI as part of a GET request. Is it possible to use it in this way?
Regards.
The text was updated successfully, but these errors were encountered: