FAQ
Does this replace ASP.NET Core Identity?
No. AuthEndpoints maps endpoints on top of Identity. You keep Identity, your user type, and EF Core.
Cookie sessions or JWT?
Both are available, and so is Identity bearer. Cookies are the default for browser apps on the password facade. See Choose your sign-in setup.
Are passkeys included?
Yes. The core package includes passkey registration, sign-in, and management. The password facade maps them when Passkeys.ServerDomain is set. Passkey sign-in skips two-factor authentication. See Passkeys and Security model.
How does 2FA work?
AuthEndpoints uses Identity's authenticator (TOTP) 2FA and 10 recovery codes. Changing 2FA settings requires step-up ReAuth. See Turn on two-factor authentication.
Can I map only some of the endpoints?
Yes. Start with the password facade, then compose modules on your own prefixes when you need a custom path or a JWT-only API. See Build a custom auth stack.
Can users sign in with GitHub or Google?
Yes, with AuthEndpoints.OAuth.GitHub and AuthEndpoints.OAuth.Google. You map their routes yourself. See Register users.
Can this be my Sign in with Google provider for other apps?
No. AuthEndpoints signs users in to your own app. If other apps need to treat you as their identity provider, use an OAuth and OpenID Connect server such as OpenIddict. See AuthEndpoints compared with MapIdentityApi and other options.
Does MapIdentityApi include a logout endpoint?
No. .NET 10 MapIdentityApi does not map /logout. The Identity API article shows a /logout route you add yourself that calls SignInManager.SignOutAsync(). That signs out the application cookie, and the external and two-factor user-id schemes when they are registered. It does not revoke Identity bearer access or refresh tokens. AuthEndpoints maps logout on each sign-in stack. Cookie POST /auth/logout requires a signed-in user and a CSRF token, and it clears the application, external, two-factor, remember-client, and ReAuth cookies. Identity bearer POST /auth/logout clears those cookies and leaves the bearer tokens valid until they expire. JWT POST /auth/logout revokes the refresh-token family and deletes the refresh cookie. The JWT access token stays valid until it expires. See Sign users out.
Can I map only some MapIdentityApi routes or rename them?
MapIdentityApi maps its full set in one call. MapGroup adds one prefix to every route. It cannot omit a route or rename /login. AuthEndpoints splits that surface into MapIdentityManagementApi, MapCookieAuthEndpoints, MapBearerAuthEndpoints, MapJwtAuthEndpoints, and MapPasskeyEndpoints. Map the modules you need. Set the prefix with MapGroup, or with Path on the password facade. The segment under that prefix stays fixed (/login, /register, /logout). A module does not let you drop one of its routes. See Build a custom auth stack.
Does MapIdentityApi return a JWT?
No. Login without useCookies or useSessionCookies returns Identity bearer tokens. They are data-protection tickets, not JWTs. Those query flags issue the application cookie instead of a token body. AuthEndpoints can issue the same Identity bearer tokens, the application cookie (the password facade default), or a separate JWT. The JWT is an access token in the response plus an HttpOnly refresh cookie. Refresh tokens are stored as hashes, rotated on use, and revoked as a family if an old token is reused. See Choose your sign-in setup.
Does MapIdentityApi include passkey endpoints?
No. .NET 10 MapIdentityApi does not map passkey routes. The Blazor Identity template has its own passkey pages. Those are not MapIdentityApi. AuthEndpoints maps passkey registration, sign-in, and management. The password facade maps them under /auth/passkeys only when Passkeys.ServerDomain is set. Passkey sign-in skips two-factor authentication. See Passkeys.