Clarify auth plan for Blazor web project template

In recent discussions, it was unclear what is committed for delivery here. Will the new Blazor web project template have auth options? If so, which ones?

Is any other integration needed between Blazor fullstack with ASP.NET Core auth? Is there an IAuthenticationStateProvider in place that just works? Is this meant to have any integration with interactive server/WebAssembly components?

[markushaslinger]

EDIT: In case anyone else finds this - I got a response from @danroth27 who clarified that the whole auth story is scheduled for rc1 now, which answers my question below.

@mkArtakMSFT is the delay only for the template part or the required packages as well? I don’t mind manually cobbling it together, so having it in the template right away is not that important.

But having the parts and being able to integrate auth is pretty essential since its integrated everywhere, from the beginning. We are planning to start implementing with preview 6 or 7 the latest - I know that’s a little early, but it’s so close to RC and I really don’t want to lock in on the old model for this new project. If you won’t be able to ship the auth packages before the RC (😭), is there at least a recommendation how to implement it (based on Blazor server style, the only thing that kind-of works at the moment) to have a somewhat manageable upgrade path? What I mean: is there a PR, branch or proposal somewhere how it’s going to look?

[markushaslinger]

I’d like to +1 that working basic auth with a transparent transition between server and wasm is needed and I very much hope you’ll manage to get it in for 8.