FAQ
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.
Cookie sessions or JWT?
Both. Cookies for a first-party web app on the same site. Identity bearer tokens for native and mobile. JWT for browser clients that want a Bearer access token with an HttpOnly refresh cookie. Pick a facade or compose one stack.
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 a 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.
AuthEndpoints NuGet package.