Hi @Anonymous ,
Thanks for your post! If you check the browser traces in the developer tools, you can see if the Correlation cookie might be getting stripped by the browser and find out why the cookie got lost. For example, this can happen if the cookie's SameSite attribute is set to "None" but the "Secure" attribute is not set as described here.
As also mentioned in the SO post, some users have been able to resolve this by adding the following in the Startup Configure method:
app.UseCookiePolicy(new CookiePolicyOptions
{
Secure = CookieSecurePolicy.Always
});
The issue may also be related to the samesitemode of the cookies. If this is the case and the samesitemode is strict, you can try setting it to this:
app.UseCookiePolicy(new CookiePolicyOptions
{
MinimumSameSitePolicy = SameSiteMode.None
});
If the app is using App.UseCookiePolicy(); in the client startup , you may also try removing that.
Additionally, this may happen if the app is not being accessed from the home page, and if this is the case it may be worth opening a support ticket to investigate your environment setup with Azure Front Door.
Let me know if this helps and if you still run into this issue. If you share the developer tool logs and network traces, I should be able to better help diagnose.
If the information helped you, please Accept the answer. This will help us as well as others in the community who may be researching similar issues.