Major Enhancement: NestJS Migration + CASL Authorization + Error Handling
Some checks failed
CI/CD Pipeline / Backend Tests (push) Has been cancelled
CI/CD Pipeline / Frontend Tests (push) Has been cancelled
CI/CD Pipeline / Build Docker Images (push) Has been cancelled
CI/CD Pipeline / Security Scan (push) Has been cancelled
CI/CD Pipeline / Deploy to Staging (push) Has been cancelled
CI/CD Pipeline / Deploy to Production (push) Has been cancelled
Some checks failed
CI/CD Pipeline / Backend Tests (push) Has been cancelled
CI/CD Pipeline / Frontend Tests (push) Has been cancelled
CI/CD Pipeline / Build Docker Images (push) Has been cancelled
CI/CD Pipeline / Security Scan (push) Has been cancelled
CI/CD Pipeline / Deploy to Staging (push) Has been cancelled
CI/CD Pipeline / Deploy to Production (push) Has been cancelled
Complete rewrite from Express to NestJS with enterprise-grade features: ## Backend Improvements - Migrated from Express to NestJS 11.0.1 with TypeScript - Implemented Prisma ORM 7.3.0 for type-safe database access - Added CASL authorization system replacing role-based guards - Created global exception filters with structured logging - Implemented Auth0 JWT authentication with Passport.js - Added vehicle management with conflict detection - Enhanced event scheduling with driver/vehicle assignment - Comprehensive error handling and logging ## Frontend Improvements - Upgraded to React 19.2.0 with Vite 7.2.4 - Implemented CASL-based permission system - Added AbilityContext for declarative permissions - Created ErrorHandler utility for consistent error messages - Enhanced API client with request/response logging - Added War Room (Command Center) dashboard - Created VIP Schedule view with complete itineraries - Implemented Vehicle Management UI - Added mock data generators for testing (288 events across 20 VIPs) ## New Features - Vehicle fleet management (types, capacity, status tracking) - Complete 3-day Jamboree schedule generation - Individual VIP schedule pages with PDF export (planned) - Real-time War Room dashboard with auto-refresh - Permission-based navigation filtering - First user auto-approval as administrator ## Documentation - Created CASL_AUTHORIZATION.md (comprehensive guide) - Created ERROR_HANDLING.md (error handling patterns) - Updated CLAUDE.md with new architecture - Added migration guides and best practices ## Technical Debt Resolved - Removed custom authentication in favor of Auth0 - Replaced role checks with CASL abilities - Standardized error responses across API - Implemented proper TypeScript typing - Added comprehensive logging Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This commit is contained in:
35
auth0-action.js
Normal file
35
auth0-action.js
Normal file
@@ -0,0 +1,35 @@
|
||||
/**
|
||||
* Auth0 Action: Add User Info to Token
|
||||
*
|
||||
* This action adds user profile information to the access token
|
||||
* so the backend can create/validate users properly.
|
||||
*
|
||||
* Deploy this in Auth0 Dashboard:
|
||||
* 1. Go to Actions → Flows → Login
|
||||
* 2. Click "+" → Build from scratch
|
||||
* 3. Name: "Add User Info to Token"
|
||||
* 4. Copy this code
|
||||
* 5. Click Deploy
|
||||
* 6. Drag into flow between Start and Complete
|
||||
* 7. Click Apply
|
||||
*/
|
||||
|
||||
exports.onExecutePostLogin = async (event, api) => {
|
||||
const namespace = 'https://vip-coordinator-api';
|
||||
|
||||
if (event.authorization) {
|
||||
// Add user profile to access token
|
||||
api.accessToken.setCustomClaim(`${namespace}/email`, event.user.email);
|
||||
api.accessToken.setCustomClaim(`${namespace}/name`, event.user.name);
|
||||
api.accessToken.setCustomClaim(`${namespace}/picture`, event.user.picture);
|
||||
api.accessToken.setCustomClaim(`${namespace}/email_verified`, event.user.email_verified);
|
||||
|
||||
// Optionally require email verification before allowing access
|
||||
// Uncomment the lines below if you want to enforce email verification
|
||||
/*
|
||||
if (!event.user.email_verified) {
|
||||
api.access.deny('Please verify your email before accessing the application.');
|
||||
}
|
||||
*/
|
||||
}
|
||||
};
|
||||
Reference in New Issue
Block a user