12

The Stack Overflow OAuth endpoints (https://stackoverflow.com/oauth/access_token/ and https://stackoverflow.com/oauth/access_token/json) have started responding to requests from the server I run my projects on with 403s and a Cloudflare CAPTCHA page, meaning users are unable to log in. This issue seems very similar to New Cloudflare protection breaking important bots.

8
  • Oddly, using wget to manually POST to the endpoints (from the same server) and providing a browser UA works correctly, returning a JSON error.
    – Ginger
    Feb 9 at 14:45
  • Feels similar to this: stackapps.com/questions/10497/…
    – rene
    Feb 9 at 14:54
  • 1
    A UserAgent that is long enough is needed, indeed.
    – rene
    Feb 9 at 14:57
  • New report on Stack Apps as well: stackapps.com/questions/10513/…
    – rene
    Feb 16 at 7:59
  • This appears to have expanded to the rest of the site as well, unfortunately. I've contacted SE personally, but haven't gotten a response yet.
    – Ginger
    2 days ago
  • Yeah, I status-reviewed the reports on Stack Apps already. Let me check if an MSE mod is around to discuss if adding more status-review tags will help.
    – rene
    2 days ago
  • 4
    I've been informed that the dev-team has the tickets on their board, I've not been given an ETA so it remains a waiting game.
    – rene
    2 days ago
  • Almost "me too!" I have the same problem but with a new personal project. In the meantime, when this issue is solved, I'm experimenting with Auth0. So far, it's working fine for my use case.
    – Rubén
    2 days ago

0

You must log in to answer this question.

Browse other questions tagged .