IFS · OAuth Scopes

IFS OAuth Scopes

OAuth 2.0 searched

IFS publishes 2 OAuth 2.0 scopes via the clientCredentials, authorizationCode, authorizationCode+PKCE, and password flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the IFS API on a user’s behalf.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

ERPField ServiceAsset ManagementManufacturingEnergyCloudSweden

Scopes: 2 Flows: clientCredentials, authorizationCode, authorizationCode+PKCE, password Method: searched

Scopes (2)

Scope	Description	Flows
openid	Standard OpenID Connect scope. Required on the token request for external integration clients.	clientCredentials, authorizationCode, authorizationCode+PKCE, password
microprofile-jwt	Requests the MicroProfile JWT claim set IFS Cloud uses for role-based access. Required alongside `openid` on the token request.	clientCredentials, authorizationCode, authorizationCode+PKCE, password

📄 Provider scope reference: https://docs.ifs.com/techdocs/26r1/030_administration/010_security/020_permission_sets/004_permission_set_overview/010_projections/

Source

OAuth Scopes

generated: '2026-09-13'
method: searched
source: https://docs.ifs.com/techdocs/26r1/030_administration/010_security/040_iam_settings/035_iam_clients/020_authenticate_external_integration/300_client_credential_flow/
docs: https://docs.ifs.com/techdocs/26r1/030_administration/010_security/020_permission_sets/004_permission_set_overview/010_projections/
supersedes:
  previous_method: derived
  previous_source: openapi/ifs-cloud-erp-openapi.yml
  reason: >-
    The previous derived file listed scopes `ifs.read` and `ifs.write` against
    https://login.ifs.cloud/oauth2/authorize. That host does not resolve (DNS NXDOMAIN,
    probed 2026-09-13) and IFS documents neither scope name. The values below are the ones
    IFS publishes.
summary: >-
  IFS Cloud does NOT express API authorization as OAuth scopes. The OIDC token request
  carries a fixed protocol scope set; what an integration is actually allowed to do is
  decided by IFS Cloud permission sets and projection grants attached to the service user,
  not by scope strings. Treat the scope list below as the complete published set — it is
  short because the model is role-based, not scope-based.
model: permission-sets
schemes:
- name: IFS IAM (OpenID Connect)
  token_endpoint: https://<SYSTEM_URL>/auth/realms/<NAMESPACE>/protocol/openid-connect/token
  flows:
  - clientCredentials
  - authorizationCode
  - authorizationCode+PKCE
  - password
scopes:
- scope: openid
  description: Standard OpenID Connect scope. Required on the token request for external integration clients.
  required: true
  flows: [clientCredentials, authorizationCode, authorizationCode+PKCE, password]
  source: https://docs.ifs.com/techdocs/26r1/030_administration/010_security/040_iam_settings/035_iam_clients/020_authenticate_external_integration/300_client_credential_flow/
- scope: microprofile-jwt
  description: >-
    Requests the MicroProfile JWT claim set IFS Cloud uses for role-based access. Required
    alongside `openid` on the token request.
  required: true
  flows: [clientCredentials, authorizationCode, authorizationCode+PKCE, password]
  source: https://docs.ifs.com/techdocs/26r1/030_administration/010_security/040_iam_settings/035_iam_clients/020_authenticate_external_integration/300_client_credential_flow/
scopes_returned_in_token:
  observed: openid audience microprofile-jwt email profile
  note: >-
    The scope string IFS shows in its documented sample token response. `audience`, `email`
    and `profile` are returned by the authorization server; only `openid microprofile-jwt`
    is documented as required on the request.
authorization_beyond_scopes:
- mechanism: Permission sets
  description: Projection grants, per-page and per-navigator grants, and per-projection access levels granted to the user or service user.
  docs: https://docs.ifs.com/techdocs/26r1/030_administration/010_security/020_permission_sets/011_creating_permission_sets/010_projections/
- mechanism: Access Control Lists (ACL)
  description: ACLs applied at projection level; projections can also be excluded outright.
  docs: https://docs.ifs.com/techdocs/26r1/030_administration/010_security/008_data_access_control/020_apply_acl_to_projection/
- mechanism: StandardEntity activation
  description: StandardEntity-class APIs require explicit activation by a system administrator before they can be used at all.
  docs: https://docs.ifs.com/policy/APIUsageCloud.pdf

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/ifs-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.