Matt
bff185e4ac
## **Fixed 502 Error After Login:** ### **Issue:** - After successful Keycloak authentication, users got 502 Bad Gateway error - Middleware was still trying to use removed useOidcAuth() composable - This caused the app to crash when accessing dashboard ### **Solution:** - Replaced useOidcAuth() with direct session API call - Uses /api/auth/session endpoint to check authentication - Maintains dual auth support (Directus + Keycloak) - Added proper error handling to prevent crashes ### **Authentication Flow Now:** 1. **Check Directus auth** first (existing users) 2. **Check custom Keycloak session** via API call 3. **Allow access** if either authentication succeeds 4. **Redirect to login** if no authentication found ### **Files Changed:** - middleware/authentication.ts - Updated to use custom auth system ## **Result:** The complete authentication flow should now work: 1. Login via Keycloak SSO 2. Token exchange and session creation 3. Middleware validates session properly 4. Dashboard loads without 502 errors ## **Ready to Test:** Deploy and test the complete SSO flow - should work end-to-end!
Client Portal
Commands
npm run devto start development
Tech Stack
- Node.js
- Nuxt
- Directus
- Vuetify