4 ms·
Thanks for the reply, good stuff. Most of this could go into part 2 I think. For part two I would definitely want at least some discussion around choice of aut
by magicalhippo 5y ago
Thanks for the reply, good stuff. Most of this could go into part 2 I think.
For part two I would definitely want at least some discussion around choice of authorization server. I realize a full deep dive is too much, but at least list the options (use a lib, use your own server, use third-party) with some pros and cons or something like that.
If you do go into token generation and usage, and mention JWT, do mention the requirement to verify the alg field against expected value. Just given the issues it's caused in the past.
Anyway, hope I wasn't being too negative, that wasn't my intention.
- mooreds 5y agoHiya, No worries, I appreciated the feedback. That's one of the magical parts of HN comments. Unfortunately part 2 is already edited and ready to go and so won't cover the choice of authorization server; it kinda assumes you are using one. Here's an HN comment I made that covers the dimensions of what to think about: https://news.ycombinator.com/item?id=26411197 https://news.ycombinator.com/item?id=26411197 I also have collected a series of essays around what to think about w/r/t outsourcing auth (including what kind of auth server to choose): https://leanpub.com/theultimateguidetooutsourcingyourauth https://leanpub.com/theultimateguidetooutsourcingyourauth . Here's a coupon for 50% off that book: hn-april . Or you can email me and I'll get you a copy; my contact info is in my profile. Thank for the feedback about JWTs. My general recommendation is to use a well vetted open source library for the signature verification, which should handle the alg check. But calling it out is a good idea.