@authhero/adapter-interfaces 3.7.0 → 3.9.0

package/dist/types/adapters/Themes.d.ts

@@ -10,6 +10,5 @@ export interface ThemesAdapter {
     create: (tenant_id: string, theme: ThemeInsert, themeId?: string, options?: CreateOptions) => Promise<Theme>;
     remove: (tenant_id: string, themeId: string) => Promise<boolean>;
     get: (tenant_id: string, themeId: string) => Promise<Theme | null>;
-    list: (tenant_id: string) => Promise<Theme[]>;
     update: (tenant_id: string, themeId: any, theme: Partial<ThemeInsert>) => Promise<boolean>;
 }

package/dist/types/adapters/Users.d.ts

@@ -1,9 +1,28 @@
 import { User, Totals, UserInsert } from "../types";
+import { AuditEventInsert } from "../types/AuditEvent";
 import { ListParams } from "../types/ListParams";
 import { CreateOptions } from "../types/ImportMetadata";
 export interface ListUsersResponse extends Totals {
     users: User[];
 }
+/**
+ * An outbox event to persist atomically with a business write. It carries a
+ * caller-assigned `id` so the enqueuer can relay it (push it onto the request's
+ * outbox-event list for delivery) without a return round-trip from the adapter.
+ */
+export type OutboxEventInsert = AuditEventInsert & {
+    id: string;
+};
+/**
+ * Options common to the event-emitting user writes. When `outboxEvents` are
+ * supplied, the adapter MUST persist them in the same atomic unit as the
+ * business write — a single `db.batch()` on D1, one transaction on
+ * kysely/better-sqlite3 — so the business row and its event row commit together
+ * or not at all (the defining guarantee of the transactional outbox pattern).
+ */
+export interface WriteOptions {
+    outboxEvents?: OutboxEventInsert[];
+}
 export interface UserDataAdapter {
     get(tenant_id: string, id: string): Promise<User | null>;
     create(tenantId: string, user: UserInsert, options?: CreateOptions): Promise<User>;
@@ -12,10 +31,13 @@ export interface UserDataAdapter {
      * registration hooks, linking, webhooks, etc.). Intended to be called from
      * inside a registration pipeline that owns hook orchestration and transaction
      * boundaries itself. The DB-level behavior is identical to `create`.
+     *
+     * Pass `options.outboxEvents` to persist post-registration outbox events in
+     * the same atomic unit as the user row.
      */
-    rawCreate(tenantId: string, user: UserInsert): Promise<User>;
-    remove(tenantId: string, id: string): Promise<boolean>;
+    rawCreate(tenantId: string, user: UserInsert, options?: WriteOptions): Promise<User>;
+    remove(tenantId: string, id: string, options?: WriteOptions): Promise<boolean>;
     list(tenantId: string, params?: ListParams): Promise<ListUsersResponse>;
-    update(tenantId: string, id: string, user: Partial<User>): Promise<boolean>;
+    update(tenantId: string, id: string, user: Partial<User>, options?: WriteOptions): Promise<boolean>;
     unlink(tenantId: string, id: string, provider: string, linked_user_id: string): Promise<boolean>;
 }

package/dist/types/types/AuditEvent.d.ts

@@ -111,6 +111,8 @@ export declare const auditEventInsertSchema: z.ZodObject<{
         body: z.ZodOptional<z.ZodUnknown>;
     }, z.core.$strip>>;
     connection: z.ZodOptional<z.ZodString>;
+    connection_id: z.ZodOptional<z.ZodString>;
+    client_name: z.ZodOptional<z.ZodString>;
     strategy: z.ZodOptional<z.ZodString>;
     strategy_type: z.ZodOptional<z.ZodString>;
     audience: z.ZodOptional<z.ZodString>;
@@ -183,6 +185,8 @@ export declare const auditEventSchema: z.ZodObject<{
         body: z.ZodOptional<z.ZodUnknown>;
     }, z.core.$strip>>;
     connection: z.ZodOptional<z.ZodString>;
+    connection_id: z.ZodOptional<z.ZodString>;
+    client_name: z.ZodOptional<z.ZodString>;
     strategy: z.ZodOptional<z.ZodString>;
     strategy_type: z.ZodOptional<z.ZodString>;
     audience: z.ZodOptional<z.ZodString>;

package/dist/types/types/Strategy.d.ts

@@ -20,3 +20,20 @@ export declare const StrategyType: {
     readonly SOCIAL: "social";
     readonly PASSWORDLESS: "passwordless";
 };
+/**
+ * The strategy value Auth0 stores on database connections. The canonical
+ * target for new connection rows; see isDatabaseConnectionStrategy for
+ * the legacy spellings still present in existing data.
+ */
+export declare const DATABASE_CONNECTION_STRATEGY = "auth0";
+/**
+ * True when a connection's `strategy` field marks it as a native database
+ * (username/password) connection.
+ *
+ * Auth0 stores database connections with `strategy: "auth0"`. Existing
+ * AuthHero data also contains two legacy spellings: the connection NAME
+ * ("Username-Password-Authentication") reused as the strategy, and the
+ * legacy provider literal ("auth2"). All readers must accept all three
+ * until connection rows are backfilled to "auth0".
+ */
+export declare function isDatabaseConnectionStrategy(strategy: string | undefined | null): boolean;

package/package.json

@@ -11,7 +11,7 @@
     "type": "git",
     "url": "https://github.com/markusahlstrand/authhero"
   },
-  "version": "3.7.0",
+  "version": "3.9.0",
   "files": [
     "dist"
   ],