Skip to content

API reference

OIDC reference

OpenID Connect (OIDC) endpoints, supported flows, request parameters, and token fields for RemiliaNET Login clients and API clients.

For an explanation of the flow, see RemiliaNET login.

Endpoints

Discovery gives the endpoint URLs and the signing keys. The discovery document of the realm also lists grants and algorithms that RemiliaNET developer clients do not use.

Supported flows

Implicit, Resource Owner Password, plain PKCE, and other grants that discovery lists are not supported for these clients. The developer portal sets the API scopes of each client. For more information, see App permissions.

Login clients

Callback URLs

  • A callback URL is registered exactly, with its scheme, port, and path.
  • Public hosts require HTTPS.
  • Local callbacks can use HTTP on localhost, 127.0.0.1, or [::1].
  • A local app cannot register a local network address or a wildcard address.
  • A Chromium extension registers https://<extension-id>.chromiumapp.org/callback.
  • The authorization request and the code exchange send the same callback URL.

Authorization parameters

Token response

ID tokens

  • An app validates an ID token with a maintained OIDC library before it uses the claims.
  • Validation checks the signature against the JSON Web Key Set (JWKS) of the issuer.
  • Validation checks the issuer, the audience, the expiry, and the saved nonce.
  • The account key is (iss, sub) from a validated ID token. Display names, handles, and email addresses can change.
  • The discovery document lists possible claims. A response can omit a claim that discovery lists.

API key clients

Token refresh

End-session parameters