Marlon Regenhardt

[fido2.targets](https://github.com/passwordless-lib/fido2-net-lib/blob/master/Src/Fido2/build/fido2.targets) seems to only exist to tell netstandard users that the lib doesn't work with net46x, as is this doc: https://github.com/passwordless-lib/fido2-net-lib/blob/master/Documentation/NET46X.md . There was an issue asking how to use...

Also what about adding net7 to the targets to get those new source generation features for people already using net7?

When the frontend lib is merged, it includes a serializer context that works in a net7 frontend too. I just tried setting the applications (Blazor server + client) to net7...

The `Fido2.BlazorWebAssembly` has the models you need, and it is indeed not published as a nuget package, not sure what is needed for that. @abergs what do we need for...

So, verify that the RpId in the attestation matches the origin of the request, or fill the options.Rp.Id from the initial request? The API could be used from multiple frontends...

...which actually breeds a whole new question I might actually try to google: What goes in the RpId when a desktop or mobile app (i.e. not a browser, not via...

Turns out, apps may use whatever as RP ID, like package name or hash of the signing key for android, although google seems to prefer people linking their app to...

Ok with #372 maybe the extra parameter for creating the options looks better.

Say a company offers three services, A, B, and C, and an identity provider Ident. You wanna login to A, so you go to a.myCo.com and login. Now to add...

Oh I see. I must admit I totally forgot you can actually work without DI and construct the thing directly. Yes that should indeed completely remove this problem, will check...