Engineering Challenges
Enforcing strict row-level authorization across four distinct roles required overriding default Strapi core controllers to dynamically inject user ownership filters, guaranteeing instructors can only access and modify their own courses[cite: 1]. Handling production authentication presented reverse-proxy obstacles on Railway where unencrypted internal HTTP connections crashed secure session cookie delivery; resolving this required configuring Koa proxy trust flags (`proxy: true`) and matching PUBLIC_URL environments. Additionally, harmonizing Google OAuth 2.0 callback routes and resolving preflight CORS restrictions between separate Vercel and Railway deployments required systematic origin configuration.