Two parallel agent-batches consolidated: USERS-MGMT (rebreak-backend agent): - Schema: Profile gets banned, bannedAt, bannedReason, deletedAt + indexes - Migration: 20260509_profile_admin_management (additive, idempotent) - DB-layer backend/server/db/adminUsers.ts: listAdminUsers (cursor-pagination, search, plan-filter) updateAdminUser (plan-validation, ban-stamping) softDeleteAdminUser (DSGVO PII-scrub: nickname=null, email=deleted-{shortid}@deleted.local) - 3 endpoints under /api/admin/users: GET (list with ?cursor&limit&q&plan&includeDeleted) PATCH /:id (plan/banned/bannedReason/lyraVoiceId) DELETE /:id (soft-delete idempotent) - 12 tests passing MODERATION (rebreak-backend agent): - Schema: CommunityPost+CommunityReply get isModerated, isDeleted, deletedAt, reportedAt + index (is_moderated, reported_at) - New ModerationAction model → audit-log table - Migration: 20260509_moderation_queue (additive, idempotent) - DB-layer backend/server/db/moderation.ts: listModerationQueue (merge posts+comments, sort by reportedAt, cursor) dismissModerationItem deleteModerationItem (content scrub + audit snapshot) banUserFromModerationItem (reuses banned/bannedAt/bannedReason fields) - 4 endpoints under /api/admin/moderation: GET /queue, POST /:id/dismiss, POST /:id/delete, POST /:id/ban-user - 11 tests passing Backend total: 78 tests passing | 4 skipped (pre-existing requireAdmin tests) Auth: x-admin-secret header (consistent with existing /admin/* endpoints). DSGVO: - Soft-delete scrubt PII statt hard-delete - Email NICHT in admin user-list (lebt nur in auth.users) - Audit-log für moderation-actions (90-day cleanup-cron pending hans-mueller-DSB-review) ⚠️ MIGRATIONS — auto-deploy via pipeline (commit b38bf17 detection): - 20260509_profile_admin_management - 20260509_moderation_queue Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
38 lines
1.4 KiB
TypeScript
38 lines
1.4 KiB
TypeScript
import { softDeleteAdminUser } from "../../../db/adminUsers";
|
|
|
|
/**
|
|
* DELETE /api/admin/users/[id] — Soft-Delete (DSGVO Art. 17, scrubbed PII)
|
|
*
|
|
* Was passiert (Details siehe db/adminUsers.ts → softDeleteAdminUser):
|
|
* - PII-Felder werden auf null gesetzt (nickname, avatar, demographics)
|
|
* - username → "deleted-{shortid}"
|
|
* - deletedAt-Marker → User taucht in normalen Listen nicht mehr auf
|
|
*
|
|
* Was NICHT passiert:
|
|
* - Hard-Delete (FK-Cascade auf Posts/Likes wäre destruktiv für Community-State)
|
|
* - Supabase auth.users Eintrag (separater Schritt — in dieser Operation
|
|
* bewusst getrennt damit kein Login-Lock vor User-Bestätigung)
|
|
*
|
|
* Auth: x-admin-secret.
|
|
* Idempotent — wiederholtes DELETE → { ok: true, alreadyDeleted: true }.
|
|
*/
|
|
export default defineEventHandler(async (event) => {
|
|
const config = useRuntimeConfig();
|
|
const secret = getHeader(event, "x-admin-secret");
|
|
if (!config.adminSecret || secret !== config.adminSecret) {
|
|
throw createError({ statusCode: 401, message: "Unauthorized" });
|
|
}
|
|
|
|
const id = getRouterParam(event, "id");
|
|
if (!id) throw createError({ statusCode: 400, message: "User-ID fehlt" });
|
|
|
|
const result = await softDeleteAdminUser(id);
|
|
|
|
// Console-audit-trail bis dedicated audit_log table verfügbar ist
|
|
console.log(
|
|
`[admin/users] DELETE (soft) user=${id} alreadyDeleted=${result.alreadyDeleted}`,
|
|
);
|
|
|
|
return result;
|
|
});
|