[Bug] PlatformNotSupportedException in HTTP client using PublicClientApplication in .NET 8 Blazor WASM about microsoft-authentication-library-for-dotnet HOT 3 CLOSED

Interesting. It looks like MSAL's HttpClient isn't compatible with WASM. Luckely you can provide your own

https://learn.microsoft.com/en-us/entra/msal/dotnet/advanced/httpclient#example-implementation

from microsoft-authentication-library-for-dotnet.

Blazor WASM is a web app framework, no? So you should use ConfidentialClientApplication.

See Public client and confidential client applications for differences between two types.

There's a Blazor WASM sample here that uses MSAL JavaScript and a Blazor Server sample here which actually uses Microsoft.Identity.Web - an simplified abstraction over MSAL.NET (recommended).

from microsoft-authentication-library-for-dotnet.

I didn't ask for explanation what Blazor WASM is and have already implemented the "right" MSAL solution using MSAL.js and MS Graph. But there are problems with it and I wanted to have full control over authentication like I have with PublicClientApplication in e.g. WPF or Web.API. I don't want to have some additional stuff done with Cookies, Session Storage etc. behind me. PublicClientApplication gives me the possibility for the same process with same sign-in dialog and all the things it offers but finally returning a response with which I can do what I want. You can also see that WPF is in first group and Web.API (confidential app) in the second one and in both cases I could test a PoC with PublicClientApplication so I don't know what you were going to point me out. I don't need to go into security details here.
I'd no like to explain all the details from the current implementation as it will take too much time, but logging-out and leaving "trash" somewhere makes my application working incorrectly for personal accounts especially after logging out. Generally using RemoteAuthenticatorView and AddAccountClaimsPrincipalFactory is what I'd like to avoid and that's the reason why I tried to implement something what just returns me a log-in result with which I can do whatever I want within the AuthenticationStateProvider.
The provided solution https://github.com/Azure-Samples/ms-identity-blazor-wasm/tree/main/WebApp-graph-user/Call-MSGraph seems to be a tricky one for me and will not solve the problems I have.
My solution would be almost fine unless
await graphClient.Me.RevokeSignInSessions.PostAsRevokeSignInSessionsPostResponseAsync();
worked for all account types including personal accounts. Unfortunately, clean log out works only for work accounts.
https://learn.microsoft.com/en-us/graph/api/user-revokesigninsessions?view=graph-rest-1.0&tabs=http

from microsoft-authentication-library-for-dotnet.