Skip to content

Authentication needs in ASP.NET Core going forward #42105

@damienbod

Description

@damienbod

Is there an existing issue for this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

https://twitter.com/davidfowl/status/1534756765597720578

Describe the solution you'd like

I see 4 authentication grouped needs in ASP.NET Core

1- Easy to implement standard client authn (OpenID Connect)
2- Standalone with cookies and ASP.NET Core Identity (IDP solutions as well)
3- Certificate auth
4- AzureAD and Azure B2C client authn

I believe Microsoft should provide templates for just the client authn and docs + links to products about how to use or implement the second and third type. The Azure AD and Azure B2C client templates are already good.

If you have simple authn templates for OIDC clients for an ASP.NET Core API, Razor page, MVC, Blazor (WASM, BFF ASP.NET Core hosted, Server) which are easy to adapt after, then we have a good solution. As part of the solution then, docs about using with different IDPs would help as all IDPs have small differences.

HTTPS should be used with all these templates per default.

Additional context

No response

Metadata

Metadata

Assignees

Labels

Pillar: Complete Blazor Webarea-authIncludes: Authn, Authz, OAuth, OIDC, BearerenhancementThis issue represents an ask for new feature or an enhancement to an existing one

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions