.ASPXANONYMOUS cookie reset when I close the browser session (window) and start up again

Question

Hi I have used Asp.Net Profile to store the anonymous user data. The application was working fine when it was hosted on Windows server 2012. We migrated the application to Windows 2019 server and since then the .ASPXANONYMOUS cookie sent down with the profile information in a Cookie reset every time I close the browser session and start up again.

I have checked the session state and Profile setting in web.config and all looks good and identical with old server. We have this a blocker issue and need to fix asap. I've been working on this from last 2 week.

Any help/guidance on this will be a great help.

Please let me know if you need more info.

Answer 1

Hi. Thank you for your question and reaching out.

I tried to conduct some research on this problem and discovered that recent reports of similar problems from other customers.
You can check the following thread:
https://techcommunity.microsoft.com/t5/discussions/cookie-bug-in-edge-as-of-oct-9-2020/m-p/1768141
https://techcommunity.microsoft.com/t5/discussions/bug-edge-stable-86-0-622-38-is-ignoring-cookies-and-site/m-p/1762596

We can tell that Microsoft engineers are aware of this issue by examining MissyQ's comment.

As a temporary workaround, make sure the Hosted app data option is not selected under edge:/settings/clearBrowsingDataOnClose.

Additionally, you can try and contact Microsoft with your input on this issue by pressing the ALT + SHIFT + I key when using the MS Edge browser.

-----------------------------------------------------------------------------------------------------------------------------------------------------

If the reply was helpful, please don’t forget to upvote or accept as answer, thank you.

Answer 2

Thank @Limitless Technology for the response. It has nothing to do with the windows version and Microsoft support is not aware of anything like this.

Just for information to whoever having similar issue:

I found the fix. This was happening due to request redirect. The cookie was getting lost when the website was getting redirected for auth and redirecting back.
I set the SameSite = none; secure and my issue got resolved.