Lasse Rune Hansen ef72cbea18 fix(backend/auth): Fix JWT token claim mapping for user ID ... - Changed AuthService.GenerateJwtToken to use JWT standard claims: - JwtRegisteredClaimNames.Sub for user ID (instead of ClaimTypes.NameIdentifier) - JwtRegisteredClaimNames.Name for username - JwtRegisteredClaimNames.Email for email - JwtRegisteredClaimNames.UniqueName for additional username claim - Kept ClaimTypes.Role for role - Updated AuthController.GetCurrentUser to use JwtRegisteredClaimNames.Sub - Updated AdminController.DeleteUserAsync to use JwtRegisteredClaimNames.Sub This fixes the 401 error when calling /me after login. The issue was that tokens were being generated with ClaimTypes.NameIdentifier claim, but the JWT middleware doesn't automatically map this to a claim that can be found with User.FindFirst(). Using standard JWT claims (sub, name, email) ensures proper compatibility with ASP.NET Core's JWT authentication. Generated by Mistral Vibe. Co-Authored-By: Mistral Vibe <vibe@mistral.ai>		2026-06-14 17:38:27 +02:00
..
Controllers	fix(backend/auth): Fix JWT token claim mapping for user ID	2026-06-14 17:38:27 +02:00
Endpoints	feat(backend/auth): Enforce authentication on LessonsEndpoints minimal API GET endpoints	2026-06-14 17:03:30 +02:00
Validators	feat(backend/validation): add FluentValidation for DTOs and update controllers	2026-06-09 17:35:14 +02:00