Changelog
Getting Started

AuthEndpoints FAQ

Does AuthEndpoints replace Identity? Cookie or JWT? Passkeys, 2FA, composing routes, and Sign in with Google as a provider.

Does this replace ASP.NET Core Identity?

No. It maps endpoints on top of Identity. You still have Identity, your user type, and EF Core.

Both. Cookies for a first-party web app on the same site. JWT or Identity bearer tokens for mobile and SPA clients. Compose one stack or both.

Are passkeys included?

Yes. WebAuthn register and login. Set Passkeys.ServerDomain in Production. Passkeys sit next to password and 2FA. They do not replace Identity.

How does 2FA work?

Through Identity's 2FA. Endpoints for enable, recovery, and step-up ReAuth. Lockout-aware login is on by default.

Can I map only some of the endpoints?

Yes. Start with the facade, then compose modules and prefixes when you need a custom path or a JWT-only API.

Can this be my Sign in with Google provider for other apps?

No. Optional GitHub and Google login into your app is AuthEndpoints.External.OAuth. If other apps need to treat you as the identity provider, that is OpenIddict (or similar), not this library.

External OAuth is a preview package with its own version. It is not included in the core AuthEndpoints NuGet package.