Why is OAuth still hard in 2023?
nango.dev
Why is OAuth still hard in 2023?
1–10 of 290 posts
Re: Why is OAuth still hard in 2023?
#2Re: Why is OAuth still hard in 2023?
#3Re: Why is OAuth still hard in 2023?
#4Re: Why is OAuth still hard in 2023?
#5Re: Why is OAuth still hard in 2023?
#6Re: Why is OAuth still hard in 2023?
#7"We support standard oauth butttt..."
Re: Why is OAuth still hard in 2023?
#8That's it. That's the end of the spec.
If you want to do anything with those tokens, you need to implement against other APIs the provider makes available. Unless all of those APIs are also standardized, it means implementing a bunch of stuff for each integration. And now things are no longer easy.
Re: Why is OAuth still hard in 2023?
#9None. They are entirely duplicative features.
But ... reason, reason, reason ... they both exist, and are going to exist, forever.
EDIT: I should say, PKCE is a functional superset of redirect URI allowlist.
Re: Why is OAuth still hard in 2023?
#10OAuth is easy in 2023. The problem is that OAuth does essentially nothing of interest by itself. It's a way to pass scoped access tokens. That's it. That's the end of the spec. If you want to do anything with those tokens, you need to implement against other APIs the provider makes available. Unless all of those APIs are also standardized, it means implementing a bunch of stuff for each integration. And now things ar…
And if you read the article, you would have something of substance to contribute on that topic, whether it is easy or hard or otherwise.