Skip to content

Latest commit

 

History

History
65 lines (45 loc) · 3.05 KB

File metadata and controls

65 lines (45 loc) · 3.05 KB

Nexus Framework

The Nexus Framework is a provider-agnostic, secure integration layer for managing OAuth 2.0 and OIDC connections. It abstracts away the complexity of managing tokens, refreshes, and provider quirks, allowing your agents and services to focus on business logic.

⚠️ Critical Configuration

The Nexus Framework requires two primary shared secrets to operate securely:

  1. ENCRYPTION_KEY: A 32-byte key used by the Broker to encrypt tokens at rest.
  2. STATE_KEY: A 32-byte key shared between the Broker and Gateway to sign and verify the OAuth state parameter.

Both services will refuse to start if these variables are missing or invalid. In distributed deployments, the STATE_KEY must be identical across all Broker and Gateway instances, or OAuth callbacks will fail with "Invalid state" errors.

Generate a secure key with: openssl rand -base64 32

Quick Start

The fastest way to get started is with Docker Compose. This will spin up the Broker, Gateway, Postgres, and Redis.

# 1. Configure environment
cp .env.example .env

# 2. Start the stack
make up

# Or if you don't have make:
docker-compose up -d --build

Client SDKs

Connect your application or MCP server to Nexus using the official SDK for your language:

Language Package Install
Go nexus-sdk go get github.com/Prescott-Data/nexus-framework/nexus-sdk@latest
TypeScript @dromos/nexus-sdk npm install @dromos/nexus-sdk
Python nexus-sdk pip install nexus-sdk

All SDKs provide full feature parity: connection management, token retrieval, MCP token injection, caching, retry logic, and structured errors.

Documentation

Quick Links