Follow-ups for passkey support in ASP.NET Core Identity

[MackinnonBuck]

#62112 adds support for passkeys in ASP.NET Core Identity and extends the Blazor Web App template to support passkey management and authentication. However, there are some follow-up items we should consider:

• Update scaffolding to include passkey support

---

• Support passwordless account creation
• Support conditional create to allow the user to seamlessly upgrade a password to a passkey after signing in
• Use the signals API to, e.g., inform the authenticator when a passkey was revoked so it doesn't get presented to the user as an option when signing in
• Make it easy to configure well-known passkey endpoints so that authenticators can automatically upgrade passwords to passkeys without requiring the customer to visit the site
• Update MapIdentityApi() to add endpoints for passkeys
• Update Microsoft.AspNetCore.Identity.UI to support the same passkey UI that got added to the Blazor Web App template

[abergs]

This issue tracks the considerations I raised here. Since my comment also adressess the API proposal I'll leave it be for now.

[mguinness]

Are there plans to integrate the new passkey support into the MapIdentityApi endpoints?

[mguinness]

Are there plans to integrate the new passkey support into the MapIdentityApi endpoints?

@mikekistler Asking if passkey support will be included the identity API endpoints via IdentityApiEndpointRouteBuilderExtensions. Maybe this could be added as a sub-issue here where it can be upvoted by others?

[mguinness]

@danroth27 - Not getting a response regarding passkey support for MapIdentityApi endpoints. Simply need to know if this is being considered or not?

[maartenba]

Can #62917 be considered?

[mikekistler]

@mguinness Sorry I missed this earlier. I agree we should add a sub issue for API support for Passkeys.

At this point we are out of runway for a feature like this to get into .NET 10. We had an item on the .NET 10 Roadmap to provide scaffolding support for the identity APIs, but this had to be dropped due to resource constraints. I believe that scaffolding support is the best strategic solution and we'll probably try again to put that out in .NET 11.