Files
novalon-website/src/lib/permissions.ts
zhangxiang a366bd1400 fix(qa): 第五轮系统性质量保障缺陷修复 + 单元/集成测试
安全/鉴权:登出清服务端 httpOnly 令牌、登录 IP 限流前置 bcrypt、停用账号
令牌在 6 个内联 role handler 失效、admin/items 存在性 oracle 认证前置、
同意偏好 sanitize fail-closed、api-crypto 按 HTTP 方法判体。

CMS:workflow 状态更新+审计收进交互式 $transaction(失败即回滚)、编辑器
richtext 走 textarea 防换行损毁、array/object 子字段按作用域读写防污染、
about/contact/erp-upgrade 补 ISR revalidate 与路由映射。

UI/a11y:AnimatedCounter 入视口前显起点、CLS 累计上报、MetricCard 动画入
effect 并卸载取消 rAF、后台状态四态映射/搜索防抖+序号守卫/媒体单 input/
吞错改横幅/表单 label-aria 关联。

新增对应判别性单测与 pagination/rate-limit/client-ip/sanitize/validate-content-data
等模块及 tests-integration 真库集成层。
2026-09-28 10:48:07 +08:00

168 lines
6.2 KiB
TypeScript
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
import { NextRequest, NextResponse } from 'next/server';
import { prisma } from '@/lib/db';
import { authenticateRequest, type JwtPayload } from '@/lib/auth';
import { unauthorized, forbidden } from '@/lib/api-response';
export type PermissionAction = 'create' | 'read' | 'update' | 'delete' | 'publish';
export interface Permission {
roleCode: string;
modelCode: string;
action: PermissionAction;
}
/**
* 判断一组角色是否对指定模型和操作具备权限
* super_admin 默认拥有所有权限
*/
export function hasPermission(
roles: string[],
modelCode: string,
action: PermissionAction,
permissions: Permission[]
): boolean {
if (roles.includes('super_admin')) return true;
return permissions.some(
(p) => roles.includes(p.roleCode) && p.modelCode === modelCode && p.action === action
);
}
/**
* 查询数据库判断指定用户是否具备权限
*/
export async function checkUserPermission(
userId: string,
modelCode: string,
action: PermissionAction
): Promise<boolean> {
// 访问令牌有效期 24h(`src/lib/auth.ts:7`),而 B-7 的账号状态校验只加在 `/api/auth/refresh` 上
// ⇒ 被停用/删除的账号在令牌过期前仍能通过每一个 guarded 路由(N-20)。
// 必须早于下面的 super_admin 短路,否则超管令牌被停用时仍放行。
const account = await prisma.user.findUnique({
where: { id: userId },
select: { status: true },
});
if (!account || account.status === 0) return false;
const userRoles = await prisma.userRole.findMany({
where: { userId },
});
const roleCodes = userRoles.map((ur) => (ur as { roleCode: string }).roleCode);
if (roleCodes.includes('super_admin')) return true;
if (roleCodes.length === 0) return false;
const permissionRecords = await prisma.permission.findMany({
where: { roleCode: { in: roleCodes } },
});
const permissions = permissionRecords.map((p) => ({
roleCode: (p as { roleCode: string }).roleCode,
modelCode: (p as { modelCode: string }).modelCode,
action: (p as { action: PermissionAction }).action,
}));
return hasPermission(roleCodes, modelCode, action, permissions);
}
/**
* 认证请求 **并** 确认账号未被停用。返回 payload 或 null(null ⇒ 调用方 unauthorized)。
*
* 为什么需要它:`authenticateRequest` 只验 JWT 签名,不看 `User.status`。N-20 把状态校验加在
* `checkUserPermission` 里,但 `admin/users` 与 `admin/roles` 这 6 个 handler 走的是「authenticateRequest
* + 内联 role 数组」而非 `requirePermission`,于是停用的 super_admin 在其 ≤24h 令牌有效期内仍能
* 列/建/改/删用户与改权限矩阵(Q-4,与 N-20 同族,只是绕开了那个已修的收口)。
* 用 `count` 而非 `findUnique` 以避开各 handler 内已有的 username 查询语义。
*/
export async function authenticateActiveRequest(
request: NextRequest
): Promise<JwtPayload | null> {
const user = authenticateRequest(request);
if (!user) return null;
const active = await prisma.user.count({
where: { id: user.userId, status: 1 },
});
if (active === 0) return null;
return user;
}
export interface PermissionSuccess {
user: JwtPayload;
}
export interface PermissionFailure {
response: NextResponse;
}
/**
* 校验请求是否已认证并具备指定权限
* 通过返回 { user },失败返回 { response }
*/
export async function requirePermission( request: NextRequest,
modelCode: string,
action: PermissionAction
): Promise<PermissionSuccess | PermissionFailure> {
const user = authenticateRequest(request);
if (!user) {
return { response: unauthorized() };
}
const allowed = await checkUserPermission(user.userId, modelCode, action);
if (!allowed) {
return { response: forbidden() };
}
return { user };
}
// ============ 账号与角色变更授权(验收 A-1 / A-2) ============
/**
* 特权角色:授予它等于交付不受限管理能力,撤销它等于把他人踢出管理面,
* 因此两个方向都必须由同等级调用者操作。与 hasPermission 的 super_admin 全权语义保持一致。
*/
export const PRIVILEGED_ROLE_CODES: readonly string[] = ['super_admin'];
export function isPrivilegedRole(roleCode: string): boolean {
return PRIVILEGED_ROLE_CODES.includes(roleCode);
}
/**
* 账号级特权护栏:返回调用者无权经手的特权角色。
*
* 口径来源 ACCEPTANCE_REVIEW_2026-09-21.md §A-2「修复」行:
* 「改密/停用他人须 super_admin;**目标持有 super_admin 时同样要求调用者为 super_admin**」——
* 条件写在「目标持有」上,而不是写在「本次请求是否改角色」上。故本函数取
* 「变更前 currentRoleCodes ∪ 变更后 resultingRoleCodes」两个状态求并集:
*
* - 撤销方向必须并入,否则 `roleCodes: ['readonly']` 覆盖掉目标原有的 super_admin 即降级,
* 与授予 super_admin 是同一类越权,只是方向相反;
* - 「调用者省略 roleCodes」同样要判定(此时 resultingRoleCodes === currentRoleCodes):
* 非超管改超管的昵称/手机号依然是对这个账号的写操作。这是**裁定过的策略而非疏漏**,
* 不可因为「角色没变」就放行 —— 详见 users/route.ts PUT 护栏处的注释。
*
* 返回空数组表示调用者有权完成该次写操作。
*
* @param callerRoleCodes 调用者角色
* @param resultingRoleCodes 写入后该账号的角色集(未提交 roleCodes 时即目标现有角色)
* @param currentRoleCodes 写入前该账号的角色集(POST 建号时为 [])
*/
export function privilegedRolesInPlay(
callerRoleCodes: string[],
resultingRoleCodes: string[],
currentRoleCodes: string[]
): string[] {
if (callerRoleCodes.includes('super_admin')) return [];
const inPlay = new Set([...resultingRoleCodes, ...currentRoleCodes]);
return [...inPlay].filter(isPrivilegedRole);
}
/**
* 改密与启停属账号接管面(A-2):`?id=` 由调用者提供,若不校验目标身份,
* content_admin 可直接替换超管口令或停用超管后登录。自助改密仍允许。
*/
export function mayChangeCredentials(callerRoleCodes: string[], isTargetSelf: boolean): boolean {
return isTargetSelf || callerRoleCodes.includes('super_admin');
}