@guren/server 2.13.0 → 2.14.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/{McpServiceProvider-D6D9nhgn.js → McpServiceProvider-BawsYjgN.js} +72 -0
- package/dist/agent/derive.d.ts +155 -0
- package/dist/agent/dispatch.d.ts +123 -0
- package/dist/agent/events.d.ts +80 -0
- package/dist/agent/redact.d.ts +55 -0
- package/dist/agent/scopes.d.ts +115 -0
- package/dist/auth/AuthManager.d.ts +64 -0
- package/dist/auth/RequestAuthContext.d.ts +3 -5
- package/dist/auth/TokenGuard.d.ts +61 -0
- package/dist/auth/api-token.d.ts +25 -5
- package/dist/auth/context.d.ts +24 -0
- package/dist/auth/index.d.ts +5 -2
- package/dist/auth/index.js +2 -2
- package/dist/auth/providers/UserProvider.d.ts +7 -0
- package/dist/auth/types.d.ts +6 -0
- package/dist/{auth-C7sVmYgc.js → auth-BSUc14CD.js} +313 -122
- package/dist/authorization/index.js +1 -1
- package/dist/authorization/middleware.d.ts +28 -1
- package/dist/{authorization-Dbcuc5ZK.js → authorization-CdfbCj8J.js} +119 -12
- package/dist/broadcasting/index.js +1 -1
- package/dist/{broadcasting-Dw-FhyjN.js → broadcasting-BxU-LIfF.js} +2 -45
- package/dist/context-DoD0c7J_.js +26 -0
- package/dist/http/middleware/auth.d.ts +2 -2
- package/dist/http/middleware/capabilities.d.ts +57 -0
- package/dist/http/middleware/csrf.d.ts +3 -0
- package/dist/http/request.d.ts +51 -2
- package/dist/index.d.ts +12 -3
- package/dist/index.js +1015 -84
- package/dist/internal/agent-preflight.d.ts +28 -0
- package/dist/internal/request.d.ts +19 -0
- package/dist/internal/request.js +2 -0
- package/dist/internal/route-path.d.ts +28 -0
- package/dist/internal/route-path.js +33 -0
- package/dist/internal/zod-compat.d.ts +201 -0
- package/dist/internal/zod-compat.js +193 -0
- package/dist/internal/zod-json-schema.d.ts +102 -0
- package/dist/internal/zod-json-schema.js +461 -0
- package/dist/mcp/create-mcp-server.d.ts +29 -0
- package/dist/mcp/index.js +1 -1
- package/dist/mvc/Controller.d.ts +46 -0
- package/dist/mvc/Router.d.ts +53 -0
- package/dist/request-CRVuIiQr.js +78 -0
- package/dist/runtime/index.js +5 -2
- package/dist/{vite-manifest-gdONBsM3.js → vite-manifest-BGfWbPYp.js} +1 -1
- package/package.json +17 -1
|
@@ -1,11 +1,24 @@
|
|
|
1
1
|
import type { Context } from 'hono';
|
|
2
2
|
import type { Model, PlainObject } from '@guren/orm';
|
|
3
3
|
import { type ModelUserProviderOptions } from './providers/ModelUserProvider.js';
|
|
4
|
+
import { type ApiTokenStore } from './api-token.js';
|
|
4
5
|
import type { AttachContextOptions, AuthContext, AuthManagerContract, AuthManagerOptions, AuthCredentials, Guard, GuardContext, GuardFactory, ProviderFactory, UserProvider } from './types.js';
|
|
6
|
+
/** How `useTokens()` configures the guard it registers. */
|
|
7
|
+
export interface ApiTokenGuardOptions {
|
|
8
|
+
/** Registered provider name used to load the full user record from a token's userId. */
|
|
9
|
+
provider?: string;
|
|
10
|
+
/** Guard registry name (defaults to 'token'). */
|
|
11
|
+
guardName?: string;
|
|
12
|
+
/** Whether verifying a bearer writes the token's `lastUsedAt`. */
|
|
13
|
+
updateLastUsed?: boolean;
|
|
14
|
+
}
|
|
5
15
|
export declare class AuthManager implements AuthManagerContract {
|
|
6
16
|
private readonly guards;
|
|
7
17
|
private readonly providers;
|
|
8
18
|
private defaultGuard;
|
|
19
|
+
private tokenGuard;
|
|
20
|
+
private apiTokenStore;
|
|
21
|
+
private apiTokenOptions;
|
|
9
22
|
constructor(options?: AuthManagerOptions);
|
|
10
23
|
registerGuard<User>(name: string, factory: GuardFactory<User>): void;
|
|
11
24
|
registerProvider<User>(name: string, factory: ProviderFactory<User>): void;
|
|
@@ -14,6 +27,15 @@ export declare class AuthManager implements AuthManagerContract {
|
|
|
14
27
|
guardNames(): string[];
|
|
15
28
|
setDefaultGuard(name: string): void;
|
|
16
29
|
getDefaultGuard(): string;
|
|
30
|
+
/**
|
|
31
|
+
* The guard name an unqualified `auth.guard()` / `auth.user()` call resolves
|
|
32
|
+
* to for this request. Explicit names always win; otherwise a registered
|
|
33
|
+
* token guard is selected when the request carries a Bearer Authorization
|
|
34
|
+
* header, falling back to the default (session) guard. This is the
|
|
35
|
+
* composite-guard rule from RFC 0016: session- and token-authenticated
|
|
36
|
+
* requests flow through the same auth surface without configuration.
|
|
37
|
+
*/
|
|
38
|
+
resolveGuardName(ctx: Context, name?: string): string;
|
|
17
39
|
createAuthContext(ctx: Context, options?: AttachContextOptions): AuthContext;
|
|
18
40
|
attempt(name: string, ctx: Context, credentials: AuthCredentials, remember?: boolean): Promise<boolean>;
|
|
19
41
|
/**
|
|
@@ -26,5 +48,47 @@ export declare class AuthManager implements AuthManagerContract {
|
|
|
26
48
|
* @param guardName - Name for the guard (defaults to 'web')
|
|
27
49
|
*/
|
|
28
50
|
useModel(model: typeof Model<PlainObject>, options?: Partial<ModelUserProviderOptions>, providerName?: string, guardName?: string): void;
|
|
51
|
+
/**
|
|
52
|
+
* Register a bearer-token guard backed by an ApiTokenStore and enable
|
|
53
|
+
* header-based guard selection: requests carrying `Authorization: Bearer`
|
|
54
|
+
* resolve to this guard, everything else keeps the default (session)
|
|
55
|
+
* guard. The default guard itself is unchanged — session apps keep
|
|
56
|
+
* working exactly as before.
|
|
57
|
+
*
|
|
58
|
+
* @param store - Where issued tokens live (see createApiToken)
|
|
59
|
+
* @param options.provider - Registered provider name used to load the full
|
|
60
|
+
* user record from the token's userId. Without it, `auth.user()` resolves
|
|
61
|
+
* to a minimal `{ id }` record (enough for Gate/policy evaluation).
|
|
62
|
+
* @param options.guardName - Guard registry name (defaults to 'token')
|
|
63
|
+
*/
|
|
64
|
+
useTokens(store: ApiTokenStore, options?: ApiTokenGuardOptions): void;
|
|
65
|
+
/**
|
|
66
|
+
* The options the last `useTokens()` call configured its guard with.
|
|
67
|
+
*
|
|
68
|
+
* Read by machinery that has to *replace* the store without changing
|
|
69
|
+
* anything else about how tokens authenticate — `guren tool:dev` installs an
|
|
70
|
+
* ephemeral store over the app's, and doing that with a bare `useTokens(store)`
|
|
71
|
+
* silently dropped the app's `provider`, so a token resolved to a bare
|
|
72
|
+
* `{ id }` instead of the real user record and every policy reading a user
|
|
73
|
+
* field behaved differently for no stated reason.
|
|
74
|
+
*/
|
|
75
|
+
getApiTokenOptions(): ApiTokenGuardOptions;
|
|
76
|
+
/**
|
|
77
|
+
* The token store {@link useTokens} was configured with, or `undefined`
|
|
78
|
+
* when this app never called it.
|
|
79
|
+
*
|
|
80
|
+
* This is the one path by which out-of-request machinery — `guren
|
|
81
|
+
* token:issue`, the App MCP adapter's principal lookup — reaches the same
|
|
82
|
+
* store the guard verifies against. `useTokens` otherwise closes over
|
|
83
|
+
* `store` inside the guard factory, where nothing outside a live request
|
|
84
|
+
* can see it, so an issuance command could only write tokens into a store
|
|
85
|
+
* of its own making, which no running app would ever read.
|
|
86
|
+
*
|
|
87
|
+
* Deliberately on this class rather than on `AuthManagerContract`: the
|
|
88
|
+
* contract describes what a *request* needs from auth, and handing out the
|
|
89
|
+
* raw store is not part of that. Callers reach it through the concrete
|
|
90
|
+
* manager (`Application.auth`).
|
|
91
|
+
*/
|
|
92
|
+
getApiTokenStore(): ApiTokenStore | undefined;
|
|
29
93
|
}
|
|
30
94
|
export type { AuthCredentials } from './types.js';
|
|
@@ -1,16 +1,14 @@
|
|
|
1
1
|
import type { Context } from 'hono';
|
|
2
2
|
import type { Session } from '../http/middleware/index.js';
|
|
3
3
|
import type { AuthContext, AuthCredentials, Guard } from './types.js';
|
|
4
|
-
export type GuardResolver = (
|
|
4
|
+
export type GuardResolver = (resolvedName: string) => Guard<unknown>;
|
|
5
5
|
export declare class RequestAuthContext implements AuthContext {
|
|
6
|
-
private readonly
|
|
6
|
+
private readonly resolveName;
|
|
7
7
|
private readonly ctx;
|
|
8
8
|
private readonly resolveSession;
|
|
9
9
|
private readonly resolveGuard;
|
|
10
10
|
private readonly guardCache;
|
|
11
|
-
constructor(
|
|
12
|
-
getDefaultGuard(): string;
|
|
13
|
-
}, ctx: Context, resolveSession: () => Session | undefined, resolveGuard: GuardResolver);
|
|
11
|
+
constructor(resolveName: (name?: string) => string, ctx: Context, resolveSession: () => Session | undefined, resolveGuard: GuardResolver);
|
|
14
12
|
guard<T = unknown>(name?: string): Guard<T>;
|
|
15
13
|
session<T extends Session = Session>(): T | undefined;
|
|
16
14
|
check(): Promise<boolean>;
|
|
@@ -0,0 +1,61 @@
|
|
|
1
|
+
import type { Context } from 'hono';
|
|
2
|
+
import type { AuthCredentials, Guard, UserProvider } from './types.js';
|
|
3
|
+
import type { Session } from '../http/middleware/index.js';
|
|
4
|
+
import { type ApiTokenStore } from './api-token.js';
|
|
5
|
+
export interface TokenGuardOptions<User = unknown> {
|
|
6
|
+
store: ApiTokenStore;
|
|
7
|
+
ctx: Context;
|
|
8
|
+
/**
|
|
9
|
+
* Resolves the token's userId to a full user record (sanitized through the
|
|
10
|
+
* provider's `sanitize` when present). Without a provider the guard still
|
|
11
|
+
* authenticates: `user()` resolves to a minimal `{ id }` record so
|
|
12
|
+
* Gate/policy evaluation (which keys on `id`) works out of the box.
|
|
13
|
+
*/
|
|
14
|
+
provider?: UserProvider<User>;
|
|
15
|
+
/** Update the token's lastUsedAt on successful verification. Default true. */
|
|
16
|
+
updateLastUsed?: boolean;
|
|
17
|
+
}
|
|
18
|
+
/**
|
|
19
|
+
* Bearer-token implementation of the Guard contract (RFC 0016 Phase 0).
|
|
20
|
+
*
|
|
21
|
+
* Reads `Authorization: Bearer <token>`, verifies it against the configured
|
|
22
|
+
* ApiTokenStore, and exposes the result through the same Guard surface the
|
|
23
|
+
* SessionGuard implements — so `requireAuthenticated()`, `Controller.auth`,
|
|
24
|
+
* and Gate resolution treat session- and token-authenticated requests
|
|
25
|
+
* identically. On successful verification the result is also written to
|
|
26
|
+
* `ctx[API_TOKEN_KEY]`, keeping `getApiToken(ctx)` and `tokenCan*` working
|
|
27
|
+
* exactly as they do behind `createBearerTokenMiddleware` — and when that
|
|
28
|
+
* middleware already verified this request's token, the guard reuses its
|
|
29
|
+
* result instead of paying a second store read and lastUsedAt write.
|
|
30
|
+
*
|
|
31
|
+
* Credential flows do not apply to bearer tokens: `attempt()`, `login()` and
|
|
32
|
+
* `validate()` throw. `logout()` is not a no-op — it revokes the presented
|
|
33
|
+
* token, the closest meaningful analogue to ending a session. On a request
|
|
34
|
+
* that carries a session cookie *and* a Bearer header, only the token is
|
|
35
|
+
* revoked; end the session explicitly via `auth.guard('web').logout()`.
|
|
36
|
+
*
|
|
37
|
+
* This guard answers authentication only. Token *abilities* are not
|
|
38
|
+
* consulted here or by Gate/policies — enforce them where the operation is
|
|
39
|
+
* dispatched (`tokenCan*`, `createBearerTokenMiddleware({ abilities })`, or
|
|
40
|
+
* the RFC 0016 scope gate), per the RFC's scope-before-policy layering.
|
|
41
|
+
*/
|
|
42
|
+
export declare class TokenGuard<User = unknown> implements Guard<User> {
|
|
43
|
+
private readonly ctx;
|
|
44
|
+
private readonly store;
|
|
45
|
+
private readonly provider?;
|
|
46
|
+
private readonly updateLastUsed;
|
|
47
|
+
private verification?;
|
|
48
|
+
private resolvedUser?;
|
|
49
|
+
constructor(options: TokenGuardOptions<User>);
|
|
50
|
+
private verify;
|
|
51
|
+
check(): Promise<boolean>;
|
|
52
|
+
guest(): Promise<boolean>;
|
|
53
|
+
user<T = User>(): Promise<T | null>;
|
|
54
|
+
id(): Promise<unknown>;
|
|
55
|
+
login(): Promise<void>;
|
|
56
|
+
attempt(_credentials: AuthCredentials, _remember?: boolean): Promise<boolean>;
|
|
57
|
+
validate(_credentials: AuthCredentials): Promise<User | null>;
|
|
58
|
+
/** Revokes the presented token. Subsequent requests with it fail verification. */
|
|
59
|
+
logout(): Promise<void>;
|
|
60
|
+
session<T extends Session = Session>(): T | undefined;
|
|
61
|
+
}
|
package/dist/auth/api-token.d.ts
CHANGED
|
@@ -131,6 +131,30 @@ export declare function parseApiToken(plainTextToken: string): {
|
|
|
131
131
|
id: string;
|
|
132
132
|
token: string;
|
|
133
133
|
} | null;
|
|
134
|
+
/**
|
|
135
|
+
* Extract the bearer token from an Authorization header value. The one
|
|
136
|
+
* parsing rule shared by `createBearerTokenMiddleware`, `TokenGuard`, and
|
|
137
|
+
* `hasBearerHeader` below — three readers of the same header must not
|
|
138
|
+
* disagree about what a bearer request is.
|
|
139
|
+
*/
|
|
140
|
+
export declare function readBearerToken(header: string | undefined | null): string | null;
|
|
141
|
+
/**
|
|
142
|
+
* The one answer to "is this request bearer-authenticated?" — the parsing
|
|
143
|
+
* rule above applied to the header it is read from. Shared by guard selection
|
|
144
|
+
* (`AuthManager.resolveGuardName`) and the CSRF skip for cookie-less bearer
|
|
145
|
+
* requests: both must classify a request identically, and a second copy of
|
|
146
|
+
* the header name is how they would drift apart.
|
|
147
|
+
*/
|
|
148
|
+
export declare function hasBearerHeader(ctx: Context): boolean;
|
|
149
|
+
/**
|
|
150
|
+
* The result of a successful bearer-token verification: the stored token
|
|
151
|
+
* record plus the fields most callers need directly.
|
|
152
|
+
*/
|
|
153
|
+
export interface VerifiedApiToken {
|
|
154
|
+
token: ApiToken;
|
|
155
|
+
userId: string | number;
|
|
156
|
+
abilities: string[];
|
|
157
|
+
}
|
|
134
158
|
/**
|
|
135
159
|
* Verify an API token and return the associated user ID.
|
|
136
160
|
*
|
|
@@ -147,11 +171,7 @@ export declare function parseApiToken(plainTextToken: string): {
|
|
|
147
171
|
*/
|
|
148
172
|
export declare function verifyApiToken(plainTextToken: string, store: ApiTokenStore, options?: {
|
|
149
173
|
updateLastUsed?: boolean;
|
|
150
|
-
}): Promise<
|
|
151
|
-
token: ApiToken;
|
|
152
|
-
userId: string | number;
|
|
153
|
-
abilities: string[];
|
|
154
|
-
} | null>;
|
|
174
|
+
}): Promise<VerifiedApiToken | null>;
|
|
155
175
|
/**
|
|
156
176
|
* Check if a token has a specific ability.
|
|
157
177
|
*/
|
|
@@ -0,0 +1,24 @@
|
|
|
1
|
+
import type { AuthContext } from './types.js';
|
|
2
|
+
/**
|
|
3
|
+
* Context key the framework auth context is stored under.
|
|
4
|
+
*
|
|
5
|
+
* Lives here rather than in `http/middleware/auth` so that `auth/` modules can
|
|
6
|
+
* import it without reaching back into the middleware layer. The middleware
|
|
7
|
+
* re-exports it, and it stays a public root export.
|
|
8
|
+
*/
|
|
9
|
+
export declare const AUTH_CONTEXT_KEY = "guren:auth";
|
|
10
|
+
/**
|
|
11
|
+
* Read the framework auth context off a request context.
|
|
12
|
+
*
|
|
13
|
+
* The lookup and its cast, in one place — nothing more. `ctx.get` returns
|
|
14
|
+
* arbitrary values for unknown keys (test doubles and exotic contexts
|
|
15
|
+
* included), so the cast is a claim, not a check. A caller whose behavior
|
|
16
|
+
* turns on the value really being an auth context probes the member it is
|
|
17
|
+
* about to call; `Gate.resolveUser` does exactly that, because a stray value
|
|
18
|
+
* there decides whether the legacy `ctx.get('user')` fallback runs. Probing
|
|
19
|
+
* here instead would reject contexts that `requireAuthenticated` and
|
|
20
|
+
* `requireGuest` can use — they only ever read `check()` / `guest()`.
|
|
21
|
+
*/
|
|
22
|
+
export declare function getAuthContext(ctx: {
|
|
23
|
+
get: (key: string) => unknown;
|
|
24
|
+
}): AuthContext | undefined;
|
package/dist/auth/index.d.ts
CHANGED
|
@@ -1,5 +1,8 @@
|
|
|
1
1
|
export { AuthManager } from './AuthManager.js';
|
|
2
|
+
export type { ApiTokenGuardOptions } from './AuthManager.js';
|
|
2
3
|
export { SessionGuard } from './SessionGuard.js';
|
|
4
|
+
export { TokenGuard } from './TokenGuard.js';
|
|
5
|
+
export type { TokenGuardOptions } from './TokenGuard.js';
|
|
3
6
|
export { BaseUserProvider } from './providers/UserProvider.js';
|
|
4
7
|
export { ModelUserProvider } from './providers/ModelUserProvider.js';
|
|
5
8
|
export { ScryptHasher } from './password/ScryptHasher.js';
|
|
@@ -10,9 +13,9 @@ export { createEmailVerificationToken, verifyEmailToken, completeEmailVerificati
|
|
|
10
13
|
export type { PasswordHasher } from './password/PasswordHasher.js';
|
|
11
14
|
export type { PasswordResetConfig, PasswordResetTokenStore, PasswordResetTokenResult, } from './password-reset.js';
|
|
12
15
|
export type { EmailVerificationConfig, EmailVerificationTokenStore, EmailVerificationToken, EmailVerificationTokenResult, } from './email-verification.js';
|
|
13
|
-
export { createApiToken, parseApiToken, verifyApiToken, tokenCan, tokenCanAll, tokenCanAny, revokeApiToken, revokeAllApiTokens, getUserApiTokens, createBearerTokenMiddleware, getApiToken, getApiTokenOrFail, MemoryApiTokenStore, API_TOKEN_KEY, } from './api-token.js';
|
|
16
|
+
export { createApiToken, parseApiToken, readBearerToken, verifyApiToken, tokenCan, tokenCanAll, tokenCanAny, revokeApiToken, revokeAllApiTokens, getUserApiTokens, createBearerTokenMiddleware, getApiToken, getApiTokenOrFail, MemoryApiTokenStore, API_TOKEN_KEY, } from './api-token.js';
|
|
14
17
|
export { OAuthManager, MemoryOAuthStateStore, createOAuthManager, createOAuthState, verifyOAuthState, buildOAuthAuthorizeUrl, exchangeOAuthCode, fetchOAuthUserProfile, createGitHubOAuthProviderConfig, createGoogleOAuthProviderConfig, createDiscordOAuthProviderConfig, buildOAuthRedirectUrl, parseOAuthRedirectUrl, sanitizeOAuthRedirect, OAUTH_SESSION_BINDING_KEY, } from './oauth/index.js';
|
|
15
|
-
export type { ApiToken, ApiTokenStore, CreateApiTokenOptions, CreateApiTokenResult, BearerTokenMiddlewareOptions, } from './api-token.js';
|
|
18
|
+
export type { ApiToken, ApiTokenStore, CreateApiTokenOptions, CreateApiTokenResult, BearerTokenMiddlewareOptions, VerifiedApiToken, } from './api-token.js';
|
|
16
19
|
export type { OAuthProviderConfig, OAuthTokenResult, OAuthUserProfile, OAuthFallbackEmail, OAuthStatePayload, OAuthStateStore, OAuthStateConfig, OAuthAuthorizeOptions, OAuthCallbackPayload, OAuthManagerOptions, OAuthProviderFactoryInput, OAuthBindingSession, } from './oauth/index.js';
|
|
17
20
|
export type { AuthContext, AuthCredentials, AuthManagerOptions, AuthManagerContract, Authenticatable, Guard, GuardContext, GuardFactory, UserProvider, ProviderFactory, AttachContextOptions, DefaultSanitizedKeys, Sanitized, } from './types.js';
|
|
18
21
|
export { hashToken, generateToken, generateId, secureCompare, secureStringCompare, buildTokenUrl, parseTokenUrl, } from './utils.js';
|
package/dist/auth/index.js
CHANGED
|
@@ -1,2 +1,2 @@
|
|
|
1
|
-
import { $ as
|
|
2
|
-
export { API_TOKEN_KEY, AuthManager, AuthenticatableModel, BaseUserProvider, MemoryApiTokenStore, MemoryEmailVerificationStore, MemoryOAuthStateStore, MemoryPasswordResetStore, ModelUserProvider, NodeHasher, OAUTH_SESSION_BINDING_KEY, OAuthManager, ScryptHasher, SessionGuard, buildOAuthAuthorizeUrl, buildOAuthRedirectUrl, buildPasswordResetUrl, buildTokenUrl, buildVerificationUrl, completeEmailVerification, completePasswordReset, createApiToken, createBearerTokenMiddleware, createDiscordOAuthProviderConfig, createEmailVerificationToken, createGitHubOAuthProviderConfig, createGoogleOAuthProviderConfig, createOAuthManager, createOAuthState, createPasswordResetToken, exchangeOAuthCode, fetchOAuthUserProfile, generateId, generateToken, getApiToken, getApiTokenOrFail, getUserApiTokens, hashToken, isEmailVerified, parseApiToken, parseOAuthRedirectUrl, parsePasswordResetUrl, parseTokenUrl, parseVerificationUrl, requireVerifiedEmail, revokeAllApiTokens, revokeApiToken, sanitizeOAuthRedirect, secureCompare, secureStringCompare, tokenCan, tokenCanAll, tokenCanAny, verifyApiToken, verifyEmailToken, verifyOAuthState, verifyPasswordResetToken };
|
|
1
|
+
import { $ as SessionGuard, A as sanitizeOAuthRedirect, B as createBearerTokenMiddleware, C as createGitHubOAuthProviderConfig, D as exchangeOAuthCode, E as createOAuthState, F as AuthManager, G as parseApiToken, H as getApiTokenOrFail, I as TokenGuard, J as revokeApiToken, K as readBearerToken, L as API_TOKEN_KEY, O as fetchOAuthUserProfile, Q as verifyApiToken, R as MemoryApiTokenStore, S as createDiscordOAuthProviderConfig, T as createOAuthManager, U as getUserApiTokens, V as getApiToken, X as tokenCanAll, Y as tokenCan, Z as tokenCanAny, _ as MemoryOAuthStateStore, a as isEmailVerified, at as secureCompare, b as buildOAuthAuthorizeUrl, c as verifyEmailToken, ct as BaseUserProvider, d as completePasswordReset, et as buildTokenUrl, f as createPasswordResetToken, g as NodeHasher, h as AuthenticatableModel, i as createEmailVerificationToken, it as parseTokenUrl, j as verifyOAuthState, k as parseOAuthRedirectUrl, l as MemoryPasswordResetStore, lt as ScryptHasher, m as verifyPasswordResetToken, n as buildVerificationUrl, nt as generateToken, o as parseVerificationUrl, ot as secureStringCompare, p as parsePasswordResetUrl, q as revokeAllApiTokens, r as completeEmailVerification, rt as hashToken, s as requireVerifiedEmail, st as ModelUserProvider, t as MemoryEmailVerificationStore, tt as generateId, u as buildPasswordResetUrl, v as OAUTH_SESSION_BINDING_KEY, w as createGoogleOAuthProviderConfig, x as buildOAuthRedirectUrl, y as OAuthManager, z as createApiToken } from "../auth-BSUc14CD.js";
|
|
2
|
+
export { API_TOKEN_KEY, AuthManager, AuthenticatableModel, BaseUserProvider, MemoryApiTokenStore, MemoryEmailVerificationStore, MemoryOAuthStateStore, MemoryPasswordResetStore, ModelUserProvider, NodeHasher, OAUTH_SESSION_BINDING_KEY, OAuthManager, ScryptHasher, SessionGuard, TokenGuard, buildOAuthAuthorizeUrl, buildOAuthRedirectUrl, buildPasswordResetUrl, buildTokenUrl, buildVerificationUrl, completeEmailVerification, completePasswordReset, createApiToken, createBearerTokenMiddleware, createDiscordOAuthProviderConfig, createEmailVerificationToken, createGitHubOAuthProviderConfig, createGoogleOAuthProviderConfig, createOAuthManager, createOAuthState, createPasswordResetToken, exchangeOAuthCode, fetchOAuthUserProfile, generateId, generateToken, getApiToken, getApiTokenOrFail, getUserApiTokens, hashToken, isEmailVerified, parseApiToken, parseOAuthRedirectUrl, parsePasswordResetUrl, parseTokenUrl, parseVerificationUrl, readBearerToken, requireVerifiedEmail, revokeAllApiTokens, revokeApiToken, sanitizeOAuthRedirect, secureCompare, secureStringCompare, tokenCan, tokenCanAll, tokenCanAny, verifyApiToken, verifyEmailToken, verifyOAuthState, verifyPasswordResetToken };
|
|
@@ -1,4 +1,11 @@
|
|
|
1
1
|
import type { AuthCredentials, Authenticatable, UserProvider } from '../types.js';
|
|
2
|
+
/**
|
|
3
|
+
* Run a user record through the provider's optional `sanitize` before it
|
|
4
|
+
* leaves the auth layer. Every guard must call this on anything it returns
|
|
5
|
+
* from `user()` — a guard that forgets the optional-chaining ternary leaks
|
|
6
|
+
* password hashes, so the ternary lives here, once.
|
|
7
|
+
*/
|
|
8
|
+
export declare function sanitizeUser<User>(provider: UserProvider<User>, user: User): User;
|
|
2
9
|
export declare abstract class BaseUserProvider<User extends Authenticatable = Authenticatable> implements UserProvider<User> {
|
|
3
10
|
abstract retrieveById(identifier: unknown): Promise<User | null>;
|
|
4
11
|
abstract retrieveByCredentials(credentials: AuthCredentials): Promise<User | null>;
|
package/dist/auth/types.d.ts
CHANGED
|
@@ -99,4 +99,10 @@ export interface AuthManagerContract {
|
|
|
99
99
|
setDefaultGuard(name: string): void;
|
|
100
100
|
getDefaultGuard(): string;
|
|
101
101
|
createAuthContext(ctx: Context, options?: AttachContextOptions): AuthContext;
|
|
102
|
+
/**
|
|
103
|
+
* The guard name an unqualified guard() call resolves to for a request.
|
|
104
|
+
* Optional for backward compatibility; implementations without it behave
|
|
105
|
+
* as if it always returned the default guard.
|
|
106
|
+
*/
|
|
107
|
+
resolveGuardName?(ctx: Context, name?: string): string;
|
|
102
108
|
}
|