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 was archived by the owner on Feb 20, 2026. It is now read-only.
In issue #15 I was asked about storing user information within the token. Of course, with only JWS, it is not safe, since user information would be stored client side. However, we could fix it by using JWE, which this library doesn't support right now.
I think this library could benefit from supporting JWE too. v2 was designed to fix performance issues with v1, but it is too verbose and doesn't allow JWE to be implemented so easily (actually, I think implementing JWE in v2 would force a major version bump anyway).
In issue #15 I was asked about storing user information within the token. Of course, with only JWS, it is not safe, since user information would be stored client side. However, we could fix it by using JWE, which this library doesn't support right now.
I think this library could benefit from supporting JWE too.
v2was designed to fix performance issues withv1, but it is too verbose and doesn't allow JWE to be implemented so easily (actually, I think implementing JWE inv2would force a major version bump anyway).References:
https://tools.ietf.org/html/rfc7516