omni-auth

Authenticate NextRoute API sessions with Bearer tokens and session cookies.

Updated Jun 6, 2026
One-click install
npx skills add https://github.com/DevMHOne/nextroute --skill omni-auth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omni-auth
Source: https://github.com/DevMHOne/nextroute/tree/main/skills/omni-auth
Command: npx skills add https://github.com/DevMHOne/nextroute --skill omni-auth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage API key authentication and session tokens to control access to the NextRoute API and ensure secure, persistent sessions.

Core Features & Use Cases

  • Bearer token authentication for all requests to /v1 endpoints.
  • Session cookies management for browser-based or long-running sessions.
  • Login configuration to enforce or relax authentication requirements in different environments.

Quick Start

Configure NEXTROUTE_URL and NEXTROUTE_KEY, then authenticate with POST /api/auth/login to obtain a Bearer token and session cookie.

Frequently Asked Questions about omni-auth

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I authenticate API requests using a Bearer token?

Authenticate API requests by configuring NEXTROUTE_URL and NEXTROUTE_KEY, then sending POST /api/auth/login to obtain a Bearer token and session cookie for authorizing subsequent /v1 endpoint calls.

How does session cookie management work for browser-based API access?

Session cookie management handles browser-based API access by issuing persistent cookies alongside Bearer tokens during the login workflow, maintaining secure long-running sessions across local and remote deployments.

Can I enforce or relax login requirements across different deployment environments?

Login configuration allows you to enforce or relax authentication requirements across different environments, applying customized access controls for local and remote NextRoute API deployments.

What is the best way to handle token refresh for persistent API sessions?

Handle token refresh for persistent API sessions by utilizing the login configuration and session management workflow, ensuring continuous Bearer token access control without manual re-authentication.

Do I need specific environment variables to start managing API session tokens?

You need to configure NEXTROUTE_URL and NEXTROUTE_KEY environment variables to start managing API session tokens and successfully obtain Bearer tokens for authentication.