App permissions
The developer portal sets the scopes of each client, and each token carries the full configured grant of its client.
Grant model
The portal attaches the configured API scopes to a Login client as default
scopes. A login request sends scope=openid, and the issued token carries the
full grant of the client.
Scopes in the authorization URL do not select a smaller grant. RemiliaNET has no per-feature incremental consent and no duration control for each permission.
A smaller grant needs a smaller client configuration. Two integrations that need different grants use separate clients. No developer API narrows the grant of an individual user. For the supported scopes, see the scope reference.
Granted scopes
The scope field of the token response lists the scopes that the user granted.
Requested scopes are not proof of a grant. RemiliaNET has no endpoint that
returns the grants of a user, so the most recent token response is the record that
your app holds. When a response has no scope field, the validated grant
information of the OpenID Connect (OIDC) library is the record. For the steps
that enable features by scope, see
Check permissions before you enable a feature.
Missing permissions
A 403 insufficient_scope response means that the token lacks a required scope.
An authorization URL alone cannot add a missing API permission. An owner can edit
the scopes of an approved client, and the portal sends saved changes to the
identity provider.
A token issued earlier does not change. The app needs another login after the configuration changes. Another login does not resolve every account or resource restriction.
Partial access
A successful login connects an account. Each API operation can require its own scope or account permission. When an optional scope is missing, the connected account, unrelated features, and drafts stay available.
A 403 response can also reflect an account restriction or a resource
restriction. The error code of the response identifies the cause, so an app does
not guess it.
Desktop browser consent
A desktop app shows consent in the system browser. A closed browser window does not show whether the user approved or canceled, so the feature stays disabled until the app receives the callback and exchanges the code. For the steps, see Add login to a local app.
