@Withings Seriously, why did you break OAuth2 compliance? support.withings.com/hc/en-u…

[BREAKING] Shutting down access and refresh tokens endpoints

Important: If you are unable to resolve your developer-related question via our public Help Center articles, please visit the Developer Dashboard here. Within the developer dashboard, you will be a...

support.withings.com
2
1
Hello, thank you for reaching out about our authentication process. Please know that OAuth2 compliance didn't break. We just changed some methods of use. If you need further assistance, please contact us at within.gs/help -Lyka
1
I believe you did. Here is an excerpt from the specification: oauth.com/oauth2-servers/acc… And here is your API reference: oauth.withings.com/api-refer… The two obviously don't match. Also, I tried to send an email through your website and it didn't work (nothing happened).

Withings

oauth.withings.com
1
lol yeah that's pretty bad, please don't ship this @Withings. That is not OAuth anymore, and it won't work with any OAuth libraries.
1
1
They already shipped it last year. The old endpoints will be shutdown in February.
1
Replying to @sagikazarmark @AskWithings @Withings
welp. abort abort!

Jan 20, 2022 · 2:30 PM UTC

1
Replying to @aaronpk @AskWithings @Withings
I'm honestly surprised that noone protested before (or they did just nothing happened?). Then again: it took me months to contact support as well.
1
If my own development patterns are any indication... I put off migrating until the last possible second because who wants to do all that work a year in advance 😅 I suspect they're about to get a bunch of angry support emails soon