Skip to content

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

https://auth.remplatforms.com

Hub API reference

auth.remplatforms.com/api/docs

Public configuration

GET /api/config (name, support address, flows, allowed return origins)

OIDC discovery, per product

https://auth.remplatforms.com/application/o/<slug>/.well-known/openid-configuration

Product registration

POST /api/products/register with a connect token

MCP

/mcp, REM's internal network only

The contract in four lines

  1. Your app registers itself at deploy with REM Auth's address and one connect token, and gets its client id and secret back.

  2. It signs people in by OIDC authorization code (with PKCE), either on REM Auth's pages or inside the app with @rem/auth-react.

  3. It keys its data by the sub claim and its permissions by the roles claim, and trusts email, groups and roles only when email_verified is true.

  4. 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

Last updated 18 Nov 2026

Developer docs · REM Platforms Blog