Authentication
NeMo Platform authenticates requests using OpenID Connect (OIDC). You register an OAuth application in your identity provider, configure NeMo Platform with the issuer and client ID, and users sign in via the CLI, SDK, or browser. NeMo Platform validates the JWT on every request and extracts the user’s identity for authorization.
For the quickstart (no IdP), see the email-based shortcut. For the authorization model, see Authorization Concepts.
Connect Your Identity Provider
Start here — register an OAuth application in your IdP and configure NeMo Platform:
- OIDC Setup — Step-by-step: register an app, configure NeMo Platform, verify login.
- Azure AD (Entra ID) — Azure-specific walkthrough (app registration, scopes, claim mapping).
- Generic OIDC Provider — Checklist for any OIDC-compliant IdP.
Log In and Make API Calls
Once your IdP is connected, see Using Authentication for the full walkthrough: device flow login, SDK and curl examples, token management, and config file reference.
The CLI stores the token and auto-refreshes it before expiry. The SDK reads the stored token from the CLI config automatically — after nemo auth login, NeMoPlatform() works with no arguments.
Discovery Endpoint
NeMo Platform exposes an unauthenticated endpoint that clients and the SDK use to discover OIDC settings:
Response:
The CLI and SDK call this endpoint automatically during nemo auth login or when initializing the client.
Related
- Using Authentication — Log in, make API calls, and manage tokens.
- Security Model — Trust boundaries and the principal model.