Developer docs
Sign people in to your app with REM Auth - OIDC endpoints, self-registration with a connect token, the @rem/auth-react SDK, user-change webhooks and the MCP server.
REM Auth is a standard OpenID Connect provider with a thin layer that lets an app connect itself.
What | Address |
|---|---|
Hub |
|
Hub API reference | |
Public configuration |
|
OIDC discovery, per product |
|
Product registration |
|
MCP |
|
The contract in four lines
Your app registers itself at deploy with REM Auth's address and one connect token, and gets its client id and secret back.
It signs people in by OIDC authorization code (with PKCE), either on REM Auth's pages or inside the app with
@rem/auth-react.It keys its data by the
subclaim and its permissions by therolesclaim, and trustsemail,groupsandrolesonly whenemail_verifiedis true.It listens to signed user-change webhooks to update or remove its records.
An app never asks for a password, never stores who has which role, and has no "users" admin of its own for sign-in.
Pages
Connect an app: connect tokens, registration, the Django helper.
Last updated 18 Nov 2026