"Microsoft.AspNetCore.Authentication.OpenIdConnect" Version="5.0.0" with .Net 5.0 blazor webassembly in VS 2019 gives NETSDK1082

[wiwichu]

If I use Nuget "Microsoft.AspNetCore.Authentication.OpenIdConnect" Version="5.0.0" with .Net 5.0 blazor webassembly in VS 2019 Version 16.8.2 I get the following error on clean: NETSDK1082 There was no runtime pack for Microsoft.AspNetCore.App available for the specified RuntimeIdentifier 'browser-wasm'.

I created a brand new blazor webassembly .Net 5.0 project. The issue occurs when I include an openidconnect reference, but disappears if I delete that reference.

[javiercn]

@wiwichu thanks for contacting us.

Microsoft.AspNetCore.Authentication.OpenIdConnect is not designed to work on the browser, hence why you are seeing that error.

Check the docs here for details on how to authenticate on Blazor webassembly.

This issue has been resolved and has not had any activity for 1 day. It will be closed for housekeeping purposes.

See our Issue Management Policies for more information.

[wiwichu]

I have actually set up an IDP (Identity Provider) and am able to authenticate, but what I want to do is after getting claims from the IDP, make a call to the app's API and get more app specific claims to merge with those from the IDP. This approach is described in a Pluralsight course by Kevin Dockx https://app.pluralsight.com/library/courses/dealing-credentials-when-securing-aspdotnet-core-3-application/table-of-contents. It uses Microsoft.AspNetCore.Authentication.OpenIdConnect, but the client is not Blazor. Do you know how I might implement this approach with a Blazor client?

Thanks,

Patrick