Framework SDKs

Framework SDKs adapt Sudomimus Connect callbacks and the Session lifecycle to a framework’s server routes, cookies, redirects, and request objects. They build on the API SDKs and use Connect directly. For other runtimes or direct API calls, choose an API SDK by language.

Next.js App RouterRoute handlers and Server Component session access.

React Router Framework ModeActions, loaders, and server-side session access.

Nuxt Node/NitroNitro server routes and server-side session access.

DjangoDjango views, sessions, callback handling, and token rotation.

All adapters require a CALLBACK ReturnRule that permits the configured callback URL. Production deployments also need a shared durable credential store; an in-memory store is suitable only for local development.

Server-only credentials

Keep the client-auth private key, refresh tokens, and returned access tokens in server-only modules and storage. Never pass them into browser components or serialize them into client-visible state.

If your framework already has a mature OpenID Connect integration, you can use the OIDC path instead. Use these adapters when you want Sudomimus Connect and its application rules directly.