Re:Grammarly's OAuth Mistakes
by jakethagle on Friday October 27, 2023 @02:49PM
(#38042366)
I'm an SE that helps software companies build integrations on top of the Prismatic platform and I've had the pleasure (or displeasure in this case) of building clients out to auth against a ton of different "flavors" of oauth.
We have a service that manages the exchange and refreshing of tokens for our customers and the number of unique implementations we're forced to support is mind boggling. I found it quite surprising how even some of the largest names in the industry have mangled their own implementations. Definitely not a "standard" in actual application.
It's clearly a difficult spec to implement, but I've witnessed that it's even more difficult for developers to learn and make use of when they're building out integrations to new systems. Unfortunately for most that do require supporting third-party integrations it becomes a necessary evil and one more burden for devs to manage and support.
I'm interested if others who have spent time dealing with a lot of third-party APIs have had similar experiences?
We have a service that manages the exchange and refreshing of tokens for our customers and the number of unique implementations we're forced to support is mind boggling. I found it quite surprising how even some of the largest names in the industry have mangled their own implementations. Definitely not a "standard" in actual application.
It's clearly a difficult spec to implement, but I've witnessed that it's even more difficult for developers to learn and make use of when they're building out integrations to new systems. Unfortunately for most that do require supporting third-party integrations it becomes a necessary evil and one more burden for devs to manage and support.
I'm interested if others who have spent time dealing with a lot of third-party APIs have had similar experiences?