views:

434

answers:

3

I'm implementing LiveID authentication on my website. I've done it before, but not on this particular platform, MojoPortal.

The sign-in works properly, but when I attempt to sign-out, I get the error message quoted below. My browser is not blocking cookies.

I get the same message when logging in to and out of, say, MSDN with a LiveID too now. I can't figure out if there's something about my site's programming that is interfering with the sign-out process of LiveID (since I believe that all (recent?) websites get sent a sign-out command) OR if live.com is just having issues lately and this is a coincidence.

Couldn't sign you out

We couldn't sign you out because your browser is blocking cookies. To sign out, close all of your browser windows.

To keep this from happening again, change your browser's settings to allow cookies. If you don't know how to do that, see your browser's help.

A: 

Purge the browser's cookie cache. I seem to recall this error can come up if a corrupted cookie gets written to the local cache.

dthorpe
I did that with all live.com cookies, but the problem persists.
uosɐſ
This may be relevant: http://social.msdn.microsoft.com/Forums/en-US/wliddev/thread/9329828e-bb96-479c-9afd-71b7416972e4
dthorpe
This really didn't fix the issue, but since I can't think of any new factors to add to tease out the solution, it would be unfair to withhold the points. (In case anyone else has the same problem)
uosɐſ
A: 

Does your browser allow third-party cookies?

michielvoo
Yes, it does...
uosɐſ
A: 

AFAICT if you block third party cookies — a not uncommon practice — then the Windows Live sign out routine presents a false alarm about signing out. In this situation the advice —

close all of your browser windows

— may be ignored. If you simply proceed to a page that requires a Windows Live ID, the prompt to sign in will appear.

Screen shots at http://www.wuala.com/grahamperrin/public/2010/09/27/a are from Chromium 6.0.443.0 (50323) after clearing all browsing data. I also tested Safari 5.0.2 in Mac OS X 10.6.x and again, found that the false alarm occurs only when third party cookies are blocked.

No mention of third party cookies at any of the following — 

— so I could be wrong …

Graham Perrin