4 ms·
OAuth's biggest issue is that unless you are regularly working with it, you'll probably forget most of the details once you're done implementing it. Similar sto
by Salgat 2y ago
OAuth's biggest issue is that unless you are regularly working with it, you'll probably forget most of the details once you're done implementing it. Similar story with regex for me, it's not that complex, but when I'm building queries a couple times a year at most, I end up forgetting it mostly. It's not surprising that most folks don't understand it, even if at one point they did in the past.
- cruffle_duffle 2y agoThere are one page regex cheat sheets you can print out and put in your workspace. Then you simply consult the cheat sheets. Unfortunately oauth cannot be compressed into a cheat sheet. But yeah, oauth is absolutely something you forget right after using it and have to bootstrap every time you touch it.
- motorest 2y ago> Unfortunately oauth cannot be compressed into a cheat sheet. What's so hard about a specific authentication flow? You have a user, a client app, a resource service, and an authorization service. You have a sequence of requests that send data back and forth. The end result is a token that client apps can send to a resource service. What bit requires volumes to understand? Take a minute to check RFC6749. All authorization flows in there require between 2 to 6 pages to fully define. Is this too much info to parse? https://datatracker.ietf.org/doc/html/rfc6749 https://datatracker.ietf.org/doc/html/rfc6749
- Salgat 2y agoYou casually gloss over the hardest part of oauth (the sequence of requests made and the reason why they exist), which is the part no one remembers.