auth-email-password

Provides email+password authentication: the always-on handlers are login, changePassword, and logout; optional flows — password reset, email verification, magic-link self-signup, and tenant invite — are registered only when you pass their respective option objects (passwordReset, emailVerification, signup, invite) to createAuthEmailPasswordFeature(opts). All four magic-link flows (reset, verification, signup activation, tenant invite) dispatch their mail through the delivery feature via ctx.notify, so mounting any of them additionally requires delivery. Tokens are HMAC-signed (reset/verify) or opaque-random in Redis (signup/invite). Requires the user and tenant features, and declares JWT_SECRET (≥ 32 chars) in authEmailPasswordEnvSchema so a missing secret surfaces at boot validation rather than on the first login attempt.

When you need it

Users sign in with email and password — login, signup, verification, and password reset on your apex surface or behind AuthGate in the admin app.

Quick example

From recipes-apex-surface-auth — the smallest working mount:

// apex-surface-auth Recipe — der evidente Weg für öffentlichen Apex-Content.
//
// Eine Kumiko-App hat eine öffentliche Apex-Präsenz (Landing/Login) UND eine
// schema-getriebene Admin-UI. Die Admin-UI mountet via createKumikoApp (volles
// Schema). Die Apex mountet via createPublicSurface — schema-LOS, anonym
// erreichbar, kein Admin-Nav/Topologie-Leak. Beide teilen Locale + Primitives.
//
// Dieses Recipe zeigt:
//   1. Server: die Feature-Komposition für die 4 Account-Flows + den anonymen,
//      email-verifizierten Deletion-Flow (Lockout-sicher).
//   2. Client (Kommentar unten + README): wie createPublicSurface + AuthShell
//      die Screens in der Apex-Chrome mounten.
//
// CLIENT-WIRING (apex.tsx der App — renderer-web, hier nur als Referenz, da
// Recipes keine Browser-Deps ziehen):
//
//   import {
//     ForgotPasswordScreen, SignupScreen, createLoginRoute,
//     AuthShellProvider, emailPasswordClient,
//   } from "@cosmicdrift/kumiko-bundled-features/auth-email-password/web";
//   import {
//     RequestAccountDeletionScreen, ConfirmAccountDeletionScreen,
//     defaultTranslations as deletionI18n,
//   } from "@cosmicdrift/kumiko-bundled-features/user-data-rights/web";
//   import { createPublicSurface } from "@cosmicdrift/kumiko-renderer-web";
//
//   // AuthShell: die Auth-Card rendert in der Marketing-Chrome statt
//   // Fullscreen. Default (ohne Provider) bleibt der Fullscreen-Wrapper.
//   const shell = ({ children }) => (
//     <MarketingChrome>
//       <AuthShellProvider shell={(card) => <div className="py-12 flex justify-center">{card}</div>}>
//         {children}
//       </AuthShellProvider>
//     </MarketingChrome>
//   );
//
//   // createLoginRoute — NICHT LoginScreen direkt rendern: die Route
//   // braucht die Challenge-Swap-Logik für einen zweiten Faktor. Ohne die
//   // (z.B. raw <LoginScreen />) bleibt ein MFA-enrolter User beim Login
//   // hängen, sobald die App irgendwann auth-mfa mountet. Mountet die App
//   // auth-mfa, `mfaVerifyScreen: MfaVerifyScreen` (aus
//   // "@cosmicdrift/kumiko-bundled-features/auth-mfa/web") ergänzen.
//   const LoginRoute = createLoginRoute({ loginScreenProps: { signupHref: "/signup" } });
//
//   createPublicSurface({
//     clientFeatures: [emailPasswordClient()],   // bringt SessionProvider + i18n
//     shell,
//     routes: [
//       { path: "/login",            component: <LoginRoute /> },
//       { path: "/signup",           component: <SignupScreen loginHref="/login" /> },
//       { path: "/forgot-password",  component: <ForgotPasswordScreen loginHref="/login" /> },
//       { path: "/delete-account",          component: <RequestAccountDeletionScreen /> },
//       { path: "/delete-account/confirm",  component: <ConfirmAccountDeletionScreen /> },
//     ],
//     fallback: <LoginRoute />,
//   });
//
//
// SERVER-WIRING: die App aktiviert `anonymousAccess` (defaultTenantId = der
// Apex-Host-Tenant), damit /api/write die anonymen Deletion-Handler erreicht:
//
//   runProdApp({ features: composeApexAccountApp({...}),
//                anonymousAccess: { defaultTenantId: APEX_TENANT_ID } })

import { createAuthEmailPasswordFeature } from "@cosmicdrift/kumiko-bundled-features/auth-email-password";
import { authFoundationFeature } from "@cosmicdrift/kumiko-bundled-features/auth-foundation";
import { createComplianceProfilesFeature } from "@cosmicdrift/kumiko-bundled-features/compliance-profiles";
import { createConfigFeature } from "@cosmicdrift/kumiko-bundled-features/config";
import { createDataRetentionFeature } from "@cosmicdrift/kumiko-bundled-features/data-retention";
import { createPersonalAccessTokensFeature } from "@cosmicdrift/kumiko-bundled-features/personal-access-tokens";
import { createSessionsFeature } from "@cosmicdrift/kumiko-bundled-features/sessions";
import { createTenantFeature } from "@cosmicdrift/kumiko-bundled-features/tenant";
import { createUserFeature } from "@cosmicdrift/kumiko-bundled-features/user";
import {
  createUserDataRightsFeature,
  type SendDeletionVerificationEmailFn,
} from "@cosmicdrift/kumiko-bundled-features/user-data-rights";
import type { FeatureDefinition } from "@cosmicdrift/kumiko-framework/engine";

export type ApexAccountAppOptions = {
  /** HMAC-Secret für das Deletion-Verify-Token. */
  readonly deletionTokenSecret: string;
  /** Apex-Route des Confirm-Screens; der Handler hängt das Token als
   *  URL-Fragment an (`#token=`). */
  readonly deletionVerifyUrl: string;
  /** Versand des Verify-Magic-Links. MUSS non-blocking sein (enqueue) — ein
   *  synchroner Send würde ein Timing-Oracle für Account-Enumeration öffnen. */
  readonly sendDeletionVerificationEmail: SendDeletionVerificationEmailFn;
};

// Volle Feature-Komposition für die öffentlichen Account-Flows. Die
// user-data-rights-Options aktivieren den anonymen Deletion-Flow; die übrigen
// Features liefern Login/Register/PW (auth-email-password) + die
// Require-Kette (user-data-rights → data-retention + compliance-profiles +
// sessions).
export function composeApexAccountApp(opts: ApexAccountAppOptions): FeatureDefinition[] {
  return [
    createConfigFeature(),
    createUserFeature(),
    createTenantFeature(),
    createAuthEmailPasswordFeature(),
    createDataRetentionFeature(),
    createComplianceProfilesFeature(),
    authFoundationFeature,
    createPersonalAccessTokensFeature({ scopes: {} }),
    createSessionsFeature(),
    createUserDataRightsFeature({
      deletionTokenSecret: opts.deletionTokenSecret,
      deletionVerifyUrl: opts.deletionVerifyUrl,
      sendDeletionVerificationEmail: opts.sendDeletionVerificationEmail,
    }),
  ];
}

📄 On GitHub: samples/recipes/apex-surface-auth/src/feature.ts

Live preview

Light Dark

How it fits

What this feature needs to run (Requires, top) and the write commands it provides (Provides, bottom).

flowchart TB
  n_auth_email_password["auth-email-password"]
  subgraph how_reqs["Requires"]
    n_user["user"]
    n_tenant["tenant"]
  end
  subgraph how_provides["Provides"]
    n_cmd_auth_email_password_write_change_password(["change-password"])
    n_cmd_auth_email_password_write_login(["login"])
    n_cmd_auth_email_password_write_logout(["logout"])
  end
  n_user --> n_auth_email_password
  n_tenant --> n_auth_email_password
  n_auth_email_password --> n_cmd_auth_email_password_write_change_password
  n_auth_email_password --> n_cmd_auth_email_password_write_login
  n_auth_email_password --> n_cmd_auth_email_password_write_logout

Provides — write commands this feature registers (dispatch them through the command bus):

• auth-email-password:write:change-password
• auth-email-password:write:login
• auth-email-password:write:logout

Getting started

Start with recipes-apex-surface-auth for a step-by-step walkthrough with runnable code and integration tests.

Try the sample

Walks through login, signup, password reset, and email verification on the public apex surface — copy the AuthGate mount and handler wiring into your app.

Dependencies

• Requires: user, tenant
• Activation: always on (not toggleable)