3 ms·
This is one instance where a naive approach may be better than a library... the two times I've written/used JWT one time I used JWE (encrypted tokens) with a pr
by tracker1 11y ago
This is one instance where a naive approach may be better than a library... the two times I've written/used JWT one time I used JWE (encrypted tokens) with a private key... the other, I only supported public/private signing (no HS256).
In practice, I tend to treat specifications as guidelines, more than absolute. I wrote a simple SCORM implementation for an eLearning software that was mainly for testing content being developed. This became the LMS for a VERY large aerospace company for about 9 years, not to mention evolving and being included as a base for several products since (over the past 12-13 years). I didn't implement the entire spec, only what was most needed for my own use. It went over 11 years before a missing piece of the spec was requested to be added.
I guess the point is, when you have something that is as relatively easy to implement as JWT, it makes sense to do it yourself, and only implement those pieces that you need.