@chidchanun/bcp 0.2.5 → 0.2.6

package/README.md

@@ -1,14 +1,14 @@
 # BCP Framework
 
-BCP Framework is a React full-stack framework for file-based routing, SSR, SPA navigation, server data loading, guarded application flows, API routes, authentication, database access, validation, uploads, storage and standalone Node.js production deployment.
+BCP Framework is a React full-stack framework for file-based routing, SSR, SPA navigation, server data loading, guarded application flows, API routes, authentication, authorization, database access, validation, uploads, storage and standalone Node.js production deployment.
 
-> **Development target:** `0.2.5 — Authentication Platform v2`
+> **Development target:** `0.2.6 — Authorization & Security v2`
 >
-> `0.2.5` is an unreleased development target until local validation, RC checks, tagging and npm publication complete.
+> `0.2.6` is an unreleased development target until local validation, RC checks, tagging and npm publication complete.
 
 ## 0.2 platform
 
-`0.2.0` established the Framework Platform baseline, `0.2.1` added the Documentation Platform, `0.2.2` added Configuration & Environment v2, `0.2.3` added Database Platform v2, `0.2.4` added Application Packaging, and `0.2.5` adds optional revocable authentication sessions and guest-aware route guards without intentionally removing the existing stateless JWT-cookie model.
+`0.2.0` established the Framework Platform baseline, `0.2.1` added the Documentation Platform, `0.2.2` added Configuration & Environment v2, `0.2.3` added Database Platform v2, `0.2.4` added Application Packaging, `0.2.5` added Authentication Platform v2, and `0.2.6` adds permission/policy authorization plus CSRF and same-origin request protection without intentionally removing the existing public application model.
 
 Machine-readable platform contracts:
 
@@ -31,8 +31,9 @@ docs/api-manifest.json
 | Routing | Static, dynamic, catch-all, optional catch-all and route groups |
 | Server data | Route `loader.ts`, request-scoped server APIs |
 | Mutations | Route-owned `actions.ts` and `<Form>` |
-| Authorization | `guard.ts`, `requireAuth()`, `requireGuest()`, `requireRole()` |
 | Authentication | JWT cookie sessions, optional server-side session stores, revocation, logout-all, idle timeout and rotation |
+| Authorization | Auth/guest/role/permission route guards, flat permissions and resource-aware policies |
+| Request security | Same-origin validation and signed CSRF tokens for unsafe mutations |
 | Middleware | Middleware System v2 with onion execution |
 | Validation | Typed validators and structured validation errors |
 | Error handling | HTTP error helpers and consistent error responses |
@@ -155,8 +156,6 @@ await db.connect();
 await db.disconnect();
 ```
 
-`db.close()` remains available for backward-compatible shutdown handling.
-
 Migration CLI:
 
 ```bash
@@ -166,8 +165,6 @@ bcp db status
 bcp db rollback
 ```
 
-BCP makes framework migration bookkeeping provider-aware. Application migration SQL itself is not automatically translated between SQL dialects.
-
 Read more:
 
 - [Database](docs/database.md)
@@ -175,7 +172,7 @@ Read more:
 
 ## Application Packaging — 0.2.4
 
-Create a fresh production build and convert it into a deployment-oriented package:
+Create a fresh production build and deployment package:
 
 ```bash
 bcp package
@@ -200,8 +197,6 @@ Output:
 └─ README.md
 ```
 
-The package layer creates production-only dependency metadata, deployment/environment manifests, SHA-256 file integrity metadata and a Node 24 Alpine Docker starter.
-
 Read more:
 
 - [Application Packaging](docs/application-packaging.md)
@@ -209,7 +204,7 @@ Read more:
 
 ## Authentication Platform v2 — 0.2.5
 
-The existing stateless JWT-cookie mode remains available:
+Stateless signed JWT-cookie authentication remains supported:
 
 ```ts
 import {
@@ -232,49 +227,149 @@ const sessionStore =
 
 export const appAuth =
     createAuth({
-        store:
-            sessionStore,
-        idleTimeout:
-            60 * 30,
+        store: sessionStore,
+        idleTimeout: 60 * 30,
     });
 ```
 
-With a store configured, authentication requires both a valid signed JWT cookie and an active `sid` record.
+With a store configured, authentication requires both a valid signed JWT cookie and an active `sid` record. The built-in memory store is intended for development/tests; production multi-instance deployments should implement `AuthSessionStore` with shared storage.
+
+Read more:
+
+- [Authentication](docs/authentication.md)
+- [Auth Session Stores](docs/auth-session-store.md)
+- [Auth Route Guards](docs/auth-route-guards.md)
+
+## Authorization & Security v2 — 0.2.6
 
-New lifecycle APIs:
+### Permissions
+
+Use flat permissions directly from `bcp/auth`:
 
 ```ts
-await appAuth.logout();
-await appAuth.logoutAll();
-await appAuth.revokeSession(sid);
-await appAuth.revokeUserSessions(userId);
-await appAuth.rotateSession();
-```
+import {
+    hasPermission,
+    requirePermission,
+} from "bcp/auth";
 
-`idleTimeout` is enforced only when a server-side store is configured. BCP rejects the option in stateless-only mode rather than silently pretending to enforce inactivity expiration.
+hasPermission(
+    user,
+    "users.read"
+);
+
+await requirePermission(
+    [
+        "users.read",
+        "users.write",
+    ],
+    {
+        match: "all",
+    }
+);
+```
 
-Guest-only login/register routes can use:
+Route trees can use a permission guard:
 
 ```ts
 import {
-    createGuestGuard,
+    createPermissionGuard,
 } from "bcp/auth";
 
 export const guard =
-    createGuestGuard({
-        redirectTo:
-            "/dashboard",
-    });
+    createPermissionGuard(
+        "admin.access"
+    );
 ```
 
-The built-in memory session store is intended for development/tests and process-local prototypes. Production applications running multiple processes or containers should implement `AuthSessionStore` with shared durable storage such as Redis or a database.
+The default permission field is `permissions`. Applications can select another field such as `scopes`.
 
-Read more:
+### Resource policies
 
-- [Authentication](docs/authentication.md)
-- [Auth Session Stores](docs/auth-session-store.md)
-- [Auth Route Guards](docs/auth-route-guards.md)
-- [JWT Sessions](docs/session-auth.md)
+For ownership, tenant or resource-state rules:
+
+```ts
+import {
+    authorize,
+    defineAuthorizationPolicy,
+} from "bcp/auth";
+
+const updateProject =
+    defineAuthorizationPolicy(
+        ({
+            user,
+            resource,
+        }) =>
+            resource.ownerId ===
+            user.id
+    );
+
+await authorize(
+    updateProject,
+    {
+        user,
+        resource: project,
+    }
+);
+```
+
+Available policy helpers:
+
+```text
+can()
+cannot()
+authorize()
+AuthorizationError
+```
+
+### Same-origin and CSRF protection
+
+Request-security helpers are exposed from `bcp/server`:
+
+```ts
+import {
+    createCsrfToken,
+    requireCsrfRequest,
+    requireSameOriginRequest,
+} from "bcp/server";
+```
+
+Protect an unsafe API/action mutation with origin validation:
+
+```ts
+await requireSameOriginRequest();
+```
+
+For signed CSRF protection:
+
+```ts
+const csrfToken =
+    await createCsrfToken();
+
+// Render/send csrfToken through the trusted application UI.
+
+await requireCsrfRequest({
+    token: submittedToken,
+});
+```
+
+Default CSRF header/cookie:
+
+```text
+X-BCP-CSRF
+bcp_csrf
+```
+
+Secret resolution:
+
+```text
+explicit options.secret
+    ↓
+BCP_CSRF_SECRET
+    ↓
+BCP_SESSION_SECRET
+```
+
+Read more: [Authorization & Security v2](docs/authorization-security.md)
 
 ## Public entrypoints
 
@@ -337,16 +432,14 @@ bcp generate middleware
 bcp generate migration create_users
 ```
 
-Page/API/middleware generators require `--force` before replacing an existing scaffold target.
-
 ## Application model
 
 ```text
 Browser
   ↓
-Security / middleware / cache
+Origin / CSRF / middleware / cache
   ↓
-Route guard
+Authentication + authorization guard
   ↓
 Loader / action / API route
   ↓
@@ -355,24 +448,6 @@ React SSR
 Hydration / SPA navigation
 ```
 
-Typical route structure:
-
-```text
-app/
-├─ layout.tsx
-├─ page.tsx
-├─ dashboard/
-│  ├─ guard.ts
-│  └─ users/
-│     └─ [id]/
-│        ├─ loader.ts
-│        ├─ actions.ts
-│        └─ page.tsx
-└─ api/
-   └─ upload/
-      └─ route.ts
-```
-
 ## Production build
 
 Raw standalone build:
@@ -388,7 +463,7 @@ Deployment package:
 bcp package
 ```
 
-Both current targets remain Node.js `standalone-node` applications. Production hardening includes configurable request/header/keep-alive/shutdown timeouts, trusted-proxy handling and graceful `SIGTERM` / `SIGINT` shutdown.
+Both current targets remain Node.js `standalone-node` applications.
 
 ## Documentation Platform
 
@@ -402,8 +477,6 @@ docs/platform-manifest.json
 docs/api-manifest.json
 ```
 
-The manifests provide navigation order, routes, Markdown sources, version/release state, public entrypoints and API guide ownership.
-
 ## Release validation
 
 Framework releases must pass:
@@ -418,7 +491,7 @@ npm run test:e2e
 npm run rc:check
 ```
 
-`0.2.5` adds Authentication Platform v2 unit and prepared-package smoke checks covering session-store registration, revocation, logout-all, idle timeout, rotation and guest guards.
+`0.2.6` adds Authorization & Security v2 unit and prepared-package smoke checks covering permission matching, policy authorization, permission route guards, same-origin mutation validation and signed CSRF tokens.
 
 Do not tag or publish until the final release commit passes the complete RC sequence.
 
@@ -438,12 +511,13 @@ Do not tag or publish until the final release commit passes the complete RC sequ
 | `0.2.3` | Database Platform v2 |
 | `0.2.4` | Application Packaging |
 | `0.2.5` | Authentication Platform v2 |
+| `0.2.6` | Authorization & Security v2 |
 
 ## Roadmap
 
-`0.2.5 — Authentication Platform v2` establishes optional revocable server-side auth state while preserving the original stateless JWT-cookie path.
+`0.2.6 — Authorization & Security v2` establishes the permission/policy and browser-mutation security layer on top of Authentication Platform v2.
 
-A later security/authorization milestone can build on this session contract for broader permission and security policy features. Native `.exe`, desktop and mobile compilation remain later roadmap work.
+The next `0.2.x` milestone can build on the existing runtime, database, auth, security and packaging contracts. Native `.exe`, desktop and mobile compilation remain later roadmap work.
 
 ## License
 

package/docs/README.md

@@ -2,7 +2,7 @@
 
 The `docs/` directory is the documentation source of truth for BCP Framework and is organized for **`bcp-docs-web`**.
 
-> **Documentation target:** BCP Framework `0.2.5 — Authentication Platform v2`
+> **Documentation target:** BCP Framework `0.2.6 — Authorization & Security v2`
 >
 > **Release state:** unreleased development target until RC validation, tagging and npm publication complete.
 
@@ -51,62 +51,67 @@ Framework source and tests remain authoritative for runtime behavior.
 | `0.2.3` | Database Platform v2 |
 | `0.2.4` | Application Packaging |
 | `0.2.5` | Authentication Platform v2 |
+| `0.2.6` | Authorization & Security v2 |
 
-## 0.2.5 — Authentication Platform v2
+## 0.2.6 — Authorization & Security v2
 
-`0.2.5` keeps stateless signed JWT-cookie authentication as the default and adds optional server-side session state for revocation and inactivity policy.
+`0.2.6` adds server-side permission checks, resource-aware authorization policies, permission route guards, same-origin mutation validation and signed CSRF protection.
 
 New/updated documentation sources:
 
 | Source | Purpose |
 | --- | --- |
-| `authentication.md` | Auth core, revocation, logout-all, rotation and idle timeout |
-| `auth-session-store.md` | `AuthSessionStore`, memory adapter and production-store guidance |
-| `auth-route-guards.md` | Auth, guest and role route guards |
-| `api-reference.md` | Public Authentication Platform v2 exports |
-| `platform-manifest.json` | Authentication v2 capability flags |
-| `api-manifest.json` | `bcp/auth` guide ownership |
-| `releases/0.2.5.md` | Authentication Platform v2 release notes |
+| `authorization-security.md` | Permissions, policies, permission guards, same-origin validation and CSRF APIs |
+| `auth-route-guards.md` | Auth/guest/role/permission route guard guidance |
+| `api-reference.md` | Public authorization and request-security exports |
+| `platform-manifest.json` | Authorization/security capability flags |
+| `api-manifest.json` | `bcp/auth` and `bcp/server` guide ownership |
+| `releases/0.2.6.md` | Authorization & Security v2 release notes |
 
-Primary public entrypoint:
+Primary authorization APIs:
 
 ```ts
 import {
-    auth,
-    createAuth,
-    createMemoryAuthSessionStore,
-    login,
-    logout,
-    logoutAll,
-    requireAuth,
-    requireGuest,
-    requireRole,
+    authorize,
+    can,
+    createPermissionGuard,
+    defineAuthorizationPolicy,
+    hasPermission,
+    requirePermission,
 } from "bcp/auth";
 ```
 
-## Authentication security model
+Primary browser-mutation security APIs:
 
-Default mode:
-
-```text
-signed HttpOnly JWT cookie
-      ↓
-signature + expiry validation
-      ↓
-authenticated session
+```ts
+import {
+    createCsrfToken,
+    requireCsrfRequest,
+    requireSameOriginRequest,
+} from "bcp/server";
 ```
 
-Optional revocable mode:
+## Security model
+
+The `0.2.6` server model separates concerns:
 
 ```text
-signed HttpOnly JWT cookie
-      +
-server-side sid store
-      ↓
-revocable authenticated session
+authentication
+    -> identify a signed/revocable session
+
+authorization
+    -> permissions + policies + route guards
+
+request security
+    -> Origin/Referer validation + signed CSRF token
+
+input validation
+    -> application schema/domain checks
 ```
 
-The built-in memory store is intended for development/tests. Multi-process production systems should implement `AuthSessionStore` using shared durable storage.
+All authorization decisions must remain server-side. Client UI permission checks may improve presentation but do not replace route/action/API enforcement.
+
+CSRF tokens use `BCP_CSRF_SECRET` when configured and otherwise fall back to `BCP_SESSION_SECRET`. Security secrets must contain at least 32 UTF-8 bytes.
 
 ## Update rule
 
@@ -130,7 +135,7 @@ Current sections:
 ```text
 Getting Started
 Routing & Data
-Authentication
+Authentication & Authorization
 Database
 Runtime & Infrastructure
 Storage & Uploads
@@ -147,10 +152,11 @@ Important current routes:
 | `/docs/authentication` | `authentication.md` |
 | `/docs/auth-session-store` | `auth-session-store.md` |
 | `/docs/auth-route-guards` | `auth-route-guards.md` |
+| `/docs/authorization-security` | `authorization-security.md` |
 | `/docs/application-packaging` | `application-packaging.md` |
 | `/docs/database` | `database.md` |
 | `/docs/api-reference` | `api-reference.md` |
-| `/releases/0.2.5` | `releases/0.2.5.md` |
+| `/releases/0.2.6` | `releases/0.2.6.md` |
 
 Every route/source pair is validated by unit tests.
 
@@ -229,7 +235,7 @@ synchronize CMS/search/navigation
 
 ## Release validation
 
-Before publishing `0.2.5`:
+Before publishing `0.2.6`:
 
 ```bash
 npm run typecheck
@@ -240,16 +246,16 @@ npm run test:e2e
 npm run rc:check
 ```
 
-Authentication Platform v2 validation covers:
+Authorization & Security v2 validation covers:
 
-- stateless JWT backward compatibility,
-- session-store registration and lookup,
-- session revocation,
-- logout-all,
-- idle timeout,
-- rotation with old-session revocation,
-- guest route guards,
-- public `bcp/auth` exports,
+- permission normalization and any/all matching,
+- permission route guards,
+- sync/async authorization policies,
+- `AuthorizationError` denial behavior,
+- same-origin mutation checks,
+- signed CSRF tokens,
+- malformed/cross-origin rejection,
+- public `bcp/auth` and `bcp/server` exports,
 - prepared npm package contents,
 - docs/platform/API version parity.
 

package/docs/api-manifest.json

@@ -1,7 +1,7 @@
 {
   "schemaVersion": 1,
   "framework": "bcp",
-  "version": "0.2.5",
+  "version": "0.2.6",
   "releaseState": "unreleased",
   "coverage": "public-entrypoints",
   "entrypoints": [
@@ -85,11 +85,12 @@
       "source": "packages/client/src/auth.ts",
       "environment": "server",
       "route": "/docs/api-reference#bcp-auth",
-      "summary": "Authentication Platform v2 with JWT cookies, optional revocable session stores, idle timeout, logout-all and auth/guest/role route guards.",
+      "summary": "Authentication Platform v2 plus permission checks, authorization policies and auth/guest/role/permission route guards.",
       "guides": [
         "/docs/authentication",
         "/docs/auth-session-store",
         "/docs/auth-route-guards",
+        "/docs/authorization-security",
         "/docs/session-auth"
       ]
     },
@@ -98,9 +99,10 @@
       "source": "packages/client/src/server.ts",
       "environment": "server",
       "route": "/docs/api-reference#bcp-server",
-      "summary": "Request context, cookies, logging, production hardening, upload, storage, response and session APIs.",
+      "summary": "Request context, cookies, CSRF/same-origin protection, logging, production hardening, upload, storage, response and session APIs.",
       "guides": [
         "/docs/server-request-apis",
+        "/docs/authorization-security",
         "/docs/file-upload",
         "/docs/storage",
         "/docs/storage-ecosystem",

package/docs/api-reference.md

@@ -164,23 +164,33 @@ Related guides: [Database](database.md), [Database Migrations](database-migratio
 
 ## `bcp/auth`
 
-Server-only Authentication Platform v2 APIs.
+Server-only authentication and authorization APIs.
 
 ```ts
 import {
+    AuthorizationError,
+    assertPermission,
     auth,
+    authorize,
+    can,
+    cannot,
     createAuth,
     createAuthGuard,
     createGuestGuard,
     createMemoryAuthSessionStore,
+    createPermissionGuard,
     createRoleGuard,
+    defineAuthorizationPolicy,
     getGuardAuth,
     getSession,
+    getUserPermissions,
+    hasPermission,
     login,
     logout,
     logoutAll,
     requireAuth,
     requireGuest,
+    requirePermission,
     requireRole,
     revokeSession,
     revokeUserSessions,
@@ -192,45 +202,71 @@ import {
     type AuthSessionStore,
     type AuthSessionStoreRecord,
     type AuthUser,
+    type AuthorizationContext,
+    type AuthorizationMatch,
+    type AuthorizationPolicy,
     type MemoryAuthSessionStore,
+    type PermissionCheckOptions,
+    type PermissionRequirement,
+    type RequirePermissionOptions,
 } from "bcp/auth";
 ```
 
-The default mode remains stateless signed JWT-cookie authentication.
+The default authentication mode remains stateless signed JWT-cookie authentication.
 
 Configure `AuthOptions.store` to enable server-side session revocation and `idleTimeout`. `createMemoryAuthSessionStore()` is provided for development/testing; production multi-instance applications should implement `AuthSessionStore` with shared durable storage.
 
-`logoutAll()`, `revokeSession()`, and `revokeUserSessions()` require server-side session state. `requireGuest()` / `createGuestGuard()` support login/register routes that should redirect already-authenticated users.
+Authorization & Security v2 adds permission checks, permission route guards and resource-aware policy functions:
 
-Related guides: [Authentication](authentication.md), [Auth Session Stores](auth-session-store.md), [Auth Route Guards](auth-route-guards.md), [JWT Sessions](session-auth.md).
+- `hasPermission()` / `assertPermission()` for flat permission or scope fields,
+- `requirePermission()` / `createPermissionGuard()` for route protection,
+- `defineAuthorizationPolicy()` for application policy definitions,
+- `can()` / `cannot()` for policy checks,
+- `authorize()` for throwing `AuthorizationError` when a policy denies access.
+
+Related guides: [Authentication](authentication.md), [Auth Session Stores](auth-session-store.md), [Auth Route Guards](auth-route-guards.md), [Authorization & Security v2](authorization-security.md), [JWT Sessions](session-auth.md).
 
 ## `bcp/server`
 
 Server request/runtime APIs.
 
-This entrypoint includes request context, cookies, logging, graceful shutdown hooks, multipart upload helpers, storage adapters, file delivery, response helpers and low-level session primitives.
+This entrypoint includes request context, cookies, CSRF and same-origin protection, logging, graceful shutdown hooks, multipart upload helpers, storage adapters, file delivery, response helpers and low-level session primitives.
 
 ```ts
 import {
     clientIp,
     cookies,
+    createCsrfToken,
     createLocalStorage,
     createLogger,
     createS3Storage,
     createStorageResponse,
+    destroyCsrfToken,
     getProductionHardeningConfig,
     headers,
+    isSafeHttpMethod,
+    isSameOriginRequest,
     json,
     redirect,
     registerShutdownHook,
     requestId,
     requestMethod,
     requestUrl,
+    requireCsrfRequest,
+    requireSameOriginRequest,
     storeMultipartFile,
+    verifyCsrfRequest,
+    verifyCsrfToken,
+    RequestSecurityError,
+    type CsrfTokenOptions,
+    type SameOriginOptions,
+    type VerifyCsrfRequestOptions,
 } from "bcp/server";
 ```
 
-Related guides: [Server Request APIs](server-request-apis.md), [File Upload](file-upload.md), [Storage](storage.md), [Storage Ecosystem](storage-ecosystem.md), [Production Hardening](production-hardening.md).
+`requireSameOriginRequest()` protects unsafe cookie-authenticated mutations by validating `Origin`/`Referer`. `createCsrfToken()` and `requireCsrfRequest()` provide signed double-submit style CSRF protection. `BCP_CSRF_SECRET` is preferred when configured and falls back to `BCP_SESSION_SECRET`.
+
+Related guides: [Server Request APIs](server-request-apis.md), [Authorization & Security v2](authorization-security.md), [File Upload](file-upload.md), [Storage](storage.md), [Storage Ecosystem](storage-ecosystem.md), [Production Hardening](production-hardening.md).
 
 ## `bcp/server-only`