Enforce JWT authentication and route boundaries in Next.js via src/proxy.ts.
npx skills add https://github.com/arunoda/OkBrain --skill auth-routing
Please help me install this Agent Skill. Skill: auth_routing Source: https://github.com/arunoda/OkBrain/tree/main/.agent/skills/auth_routing Command: npx skills add https://github.com/arunoda/OkBrain --skill auth-routing
This Skill addresses the need for robust authentication and request routing in Next.js applications, ensuring that only authorized users can access protected resources.
/login page and /api/auth/login endpoint, redirecting any unauthenticated user attempting to access other routes to the login page.Add the '/new-public-route/' path to the publicPaths array in src/proxy.ts to make it accessible without authentication.
High-intent search queries and answers about installing and using this skill.
JWT authentication in Next.js is enforced by intercepting requests through a proxy middleware that verifies user sessions via JWT cookies before allowing access to protected application routes and API endpoints. Unauthenticated API calls receive a 401 response.
To make specific Next.js routes public, add the desired path, such as `/new-public-route/`, to the `publicPaths` array in `src/proxy.ts`. This excludes specified routes from JWT authentication checks while keeping other application paths protected.
When unauthenticated users access protected Next.js routes, the proxy routing mechanism handles unauthorized access by returning a 401 status for API calls or redirecting browser navigation to the `/login` page for other application routes.
Yes, proxy routing manages authentication and routing boundaries directly within Next.js applications using `src/proxy.ts`. It intercepts requests to modify headers, perform redirects, or return specific error responses without requiring external middleware dependencies.
Next.js proxy routing supports custom login endpoints by excluding specific public paths like `/login` and `/api/auth/login` from authentication enforcement. This allows users to access login functionality while securing the rest of the application.
Proxy routing provides a centralized authentication boundary in `src/proxy.ts` that explicitly handles JWT cookie verification, public path exclusion, and differentiated responses for API versus application routes, ensuring robust access control for protected resources.
GabeujinIntegrate a new language into a Next.js app using next-intl.
salavenderImplement JWT, cookie, and MFA authentication workflows with RBAC and audit logging.
djankiesMigrate Next.js 16 middleware.ts to proxy.ts with renamed exports and relocated auth logic.
dr-codeImplement NextAuth v5 authentication and authorization for Next.js applications.