Introduction
AuthEndpoints maps ready-made auth API endpoints on top of ASP.NET Core Identity. It is for a first-party API. Your own web and mobile clients sign in to your own backend. You keep Identity, your user type, and EF Core. AuthEndpoints adds the routes, the rate limits, the CSRF checks, and the step-up flow.
The home page lists what AuthEndpoints can do. The task list is I want to.
One fast path
Most new hosts start with the password facade. Quick start goes from an empty project to cookie sign-in with AddPasswordAuth, UseAuthEndpoints, and MapPasswordAuth.
When that setup is not the one you need, open Choose your sign-in setup. The table there matches a need to one call and one page: cookie or JWT, passkeys, an emailed code, GitHub or Google, or a custom mix of Add* and Map* pairs.
Facade or composition
The password facade is one fixed composition. It maps password sign-up, sign-in, recovery, and account management under /auth.
Composition is the same building blocks with the prefixes and the mix you choose. The pairs are in the composition table. Why the blocks split that way is in Build a custom auth stack.
GitHub and Google sign-in ships in AuthEndpoints.OAuth.GitHub and AuthEndpoints.OAuth.Google 4.x. Those packages register the handlers. The endpoints are in the core package. The password facade does not map them.
When not to use AuthEndpoints
AuthEndpoints is built for first-party SPAs and APIs: your own clients sign in to your own backend. It does not issue tokens to third-party clients.
For single sign-on across applications, OAuth for third-party clients, or a full identity server, use one of these:
Requirements
- .NET 10
- ASP.NET Core Identity
- EF Core for the user store
Next
To report a vulnerability, see the security policy.