OIDC endpoints and claims
The live OpenID Connect endpoints, grant types, scopes and the claims REM Auth puts in tokens - including the verified-email rule.
Each product has its own issuer. For the product payments the live discovery document is:
curl https://auth.remplatforms.com/application/o/payments/.well-known/openid-configurationField | Value |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
scopes |
|
Replace payments with your product's slug.
Sign in (authorization code + PKCE)
GET https://auth.remplatforms.com/application/o/authorize/
?response_type=code
&client_id=<client id>
&redirect_uri=https://yourapp.com/api/auth/oidc/callback
&scope=openid%20email%20profile%20offline_access
&state=<random>
&code_challenge=<BASE64URL(SHA256(verifier))>&code_challenge_method=S256REM Auth runs its own screens (branded with your product's name), then redirects to redirect_uri with code and state. Exchange the code on your server:
curl -X POST https://auth.remplatforms.com/application/o/token/ \
-u "$CLIENT_ID:$CLIENT_SECRET" \
-d grant_type=authorization_code -d code="$CODE" \
-d redirect_uri=https://yourapp.com/api/auth/oidc/callback -d code_verifier="$VERIFIER"The answer has id_token, access_token, refresh_token (with offline_access) and expires_in. Keep tokens on your server or in an encrypted httpOnly cookie; never in a URL or browser storage. Machine-to-machine calls can use the client_credentials grant with the same client.
Claims
Claim | Scope | Meaning |
|---|---|---|
| openid | Stable, per-product user id. Key your data by it. |
|
| |
| profile | The central profile |
| profile | The person's teams (a team counts as its parent group) |
| profile | Your product's roles, from the Access table. Empty while the e-mail is unverified. |
Linking rule for existing accounts: link by sub once linked; link an existing local account by e-mail only when email_verified is true, and never re-link by e-mail later. Refuse unverified sign-ins if your app needs a real address.
Sign out
Send the browser to signout_url from registration (https://auth.remplatforms.com/logout?app=<slug>): it ends the REM Auth session and lands on your product's after-sign-out address. RP-initiated logout through end_session_endpoint with post_logout_redirect_uri works too.
Check a token or read the profile
POST /application/o/introspect/ with your client credentials, or GET https://auth.remplatforms.com/api/profile with the person's access token.
Last updated 18 Nov 2026