You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 11, 2024. It is now read-only.
Yep, big token size is a problem with JWT. For smaller token sizes you could use for example Branca tokens together with MessagePack payload. This is what I am using these days unless project spec specifically says the token must be a JWT. My use case is often the same as yours, API keys which contain some extra data.
I like what i see on Branca. ;) Will implement this on my current project.
Still, the callback before the token gets validated might make sense, doesn't it?
For the above mentioned usecase md5 would not work since it is a hashing algorithm. It is one way only. You can make a hash from the token but you cannot make the token from the hash. Base64 also would not help since JWT already is Base64 encoded.
Did not test but. What might help is compressing the token with LZW or something similar and then Base64 encoding it. However now the token is not JWT anymore, it is something else.
Hey,
following Use Case:
If have not seen any possibility in your code yet, did i miss anything?
Might be a small Usecase, but a setting with a callback function to modify the token before it is extracted might be nice.
Greets!
The text was updated successfully, but these errors were encountered: