server-authentication

JWT authentication for session management requires issuing short-lived access tokens and long-lived refresh tokens. This skill implements that flow by providing an auth context to manage token state and auto-activating when you work on auth-related files.

Protecting routes against unauthorized access involves validating JWT tokens before granting entry to protected resources. This skill provides route guards that intercept requests, verify token validity, and redirect unauthenticated users to simplify login workflows.

Handling JWT login and logout workflows involves generating tokens upon successful authentication and invalidating them during logout. This skill streamlines these processes by managing token storage and providing an authentication context for easy state management.

Yes, JWT authentication patterns can auto-activate based on file types. This skill detects when you are working on specific auth-related files and folders, automatically providing the necessary secure access and refresh token patterns without manual activation.

Manually configuring route guards is minimized with this skill. It provides built-in route protection mechanisms that detect JWT authentication patterns and apply the necessary session control logic to prevent unauthorized access automatically.

JWT session management requires both access and refresh tokens to balance security and user experience. Short-lived access tokens protect against interception, while refresh tokens allow users to maintain sessions without repeatedly logging in, a pattern this skill implements.