17

Recently (as in, the last few hours - however, it may have been broken for a few days), I've been unable to login via Stack Exchange for a third party application with Stack Exchange's OAuth support. When attempting to login, I'm presented with the following error screen:

enter image description here

Transcription of the error page:

Application Login Failure

An error occurred while login into an application.

Error Details

error: invalid_request
error description: OAuth request must be over HTTPS

Note that the URL is HTTPS, and so is the redirect_uri.

I've reproduced this on two independently developed applications and on two distinct networks (my work machine, and mobile).

  • 1
    Happens on MetaSmoke (Charcoal Teams report). – Stormblessed Nov 1 at 19:25
  • Does this happen on stackoverflow.com/oauth ? Note: the docs do not use stackexchange.com :) – Nick Craver Nov 1 at 19:50
  • A tweak for this route is going out now which should resolve your issue (please report back! - I don't want to mark this status-completed until we confirm you're good). Overall, migrating to stackoverflow.com/oauth will be the supported way - we'll be removing the old stackexchange.com path eventually as part of overall infrastructure cleanup (leaving only redirects). – Nick Craver Nov 1 at 20:25
  • @Nick it’s fixed!! Thanks! – Stormblessed Nov 1 at 21:23
  • @NickCraver Oh, I hadn't noticed the documentation had changed, I'd just re-used code from a few years ago. I'll make sure to get the endpoint updated, thanks! – ert Nov 2 at 4:56
8

This was a bug that crept in as part of the .NET Core migration (the only one I’m aware of, so close!). Sorry about that, a fix has been deployed now. Note that we’ll redirect these URLs but the preferred method in the docs is using stackoverflow.com instead as your endpoint (its a different app on our backend).

Thanks for the quick report, it’s much appreciated!

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .