Blazor Webassembly under Google Chrome with 3rd-party cookies blocked enabled not working

Michael Joseph 96 Reputation points
2021-02-23T06:09:41.567+00:00

With Cross-Site Tracking enabled on Safari, and also under Google Chrome with 3rd-party cookies blocked, my Blazor webassembly PWA is not working as expected. I am using Identity Server 4 deployed as a separate website and domain, as it is the IDP for both my Blazor application and for a separate web site.

For example, immediately after I've logged on, a web service call works as expected and returns results to the UI. However, if I wait for 30 or 40 seconds or so, it misbehaves and results are not delivered. In the failing case, inspecting the browser network activity on Chrome, I still see two successful web service calls (result code 200) both to the same endpoint one initiated by dotnet.3.2.0.js and the second by service-worker.js. However the network Response for service-worker.js is empty. I have PKCE enabled on IS4 for my Blazor client. I attach the app's OIDC configuration.

70869-oidc.txt

Thanks.

Blazor
Blazor
A free and open-source web framework that enables developers to create web apps using C# and HTML being developed by Microsoft.
1,479 questions
0 comments No comments
{count} votes

Accepted answer
  1. Michael Joseph 96 Reputation points
    2021-02-23T06:14:11.687+00:00

    I should clarify that the browser settings 'Prevent Cross-Site Tracking' on Safari, and 'Block third-party Cookies' on Google both yield similar problems.


0 additional answers

Sort by: Most helpful