0

After I logout from my Outlook account, I get high frequency of "signing out error" reports, with the following message:

Hmm... we're having trouble signing you out. You may still be signed in to some applications. Close your browser to finish signing out. Or, head back to outlook.com.

My question, whether this problem could be an indication that someone else in signed into the account?

  • 1
    Better ask Outlook.com support directly. It's quite curious that there are websites that you cannot signed out from... – billc.cn Aug 31 '16 at 16:11
  • As a quick solution you could clear your web browser's "cookies and cache" it's possible a JS file went corrupt in transit or a cookie's session went haywire. I'm still curious about why you are having the issue. – Nathaniel Suchy Aug 31 '16 at 20:41
  • Thanks for the suggestions! I log-in to the account from a single device. That's why it's puzzling why I can't log-out correctly. Inability to log-out, could mean (theoretically) that someone else simultaneously connects the account from another device, or exploit still ongoing traffic to the account to gain access to it later on. Either way, it's highly underestimated vulnerability of many email providers. If the problem persists, I will contact outlook support team. – HelpDesk Sep 4 '16 at 13:15
0

I am getting this error but only under one condition. I am pointing users to a URL which skips home realm discovery:

https://login.microsoftonline.com/login.srf?wa=wsignin1.0&whr=**domain.name**

Signing in works perfectly, and after this I'm redirected to the Office Portal, but when I press “Sign Out” on the Office Portal, I get a “Hmm… we’re having trouble signing you out.” error.
This is something to do with the fact that the above URL creates a WS-FED session and Office Portal is then generates an OpenID Connect session. Sign Out requests an OIDC sign-out and interestingly enough also a WS-FED sign-out session with a wa=wsignoutcleanup1.0 parameter, but something most likely does not detect the end of the WS-Fed session, hence the error.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.