Last post Feb 19, 2014 09:37 PM by AndyW2009
Jan 30, 2014 03:52 PM|AndyW2009|LINK
Just some general feedback. Every now and again when I read a post I will get auto-signed out from the forum (it doesnt refresh the page, but if I click 'reply' to a thread I get taken to a page where I need to enter some credentials and a capture text.
No matter what I do, I cannot login unless I close the browser and sign in again normally - it then continues working as normal.
It has happened a few times now so I though I would mention it. Using the Microsoft account signin process.
Jan 30, 2014 04:23 PM|Rion Williams|LINK
Could you elaborate a bit more regarding the browser (and version) that you are using any any settings that might be relevant? Do you have any particular settings such as your Cookies being disabled or something similar?
Jan 31, 2014 10:48 AM|tmorton|LINK
I've done some testing and have been able to repro what you are describing. These are the steps I followed:
When I follow these steps, I wind up on this page: https://login.asp.net/login/createuser.aspx, which is "Join Our Community". This page is prompting you to create a new account, and includes a captcha.
Anything you try to do from here fails (creating a new account, associating an existing account, clicking Forums then attempting to Sign In).
This is happening because the site authentication cookie is removed, but the Windows Live Connect session cookie (login.asp.net, wl_auth) is still present. So you are in a weird in-between state of being semi-authenticated. If you delete this wl_auth cookie,
you will then be able to log in again without closing your browser. Or, you can close your browser as you have done.
I have no idea why your _msc_aspnet cookie is disappearing. The expiration date is set months into the future. After I logged in today the expiration date for mine was set to 10/04/2014. My guess is that there is something in your local environment which
is removing the cookie.
Feb 19, 2014 09:37 PM|AndyW2009|LINK
Hi thanks for your replies. THe issue appears to have gone away, so I suspect it was the result of a temporary networking issue.