Queensland University of Technology OAuth Scopes

OAuth 2.0 derived

Queensland University of Technology uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

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.

UniversityHigher EducationEducationAustraliaResearchResearch RepositoryIdentity FederationOAI-PMHSAMLOpenID ConnectInstitutional RepositoryOpen Access
Scopes: 0 Flows: Method: derived

Scopes (0)

Queensland University of Technology implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

Source

OAuth Scopes

Raw ↑
# This file was generated by API Evangelist for the qut profile on 2026-09-01. It was NOT published
# by Queensland University of Technology. The `method:` key states how the content was obtained and
# `source:` names the live URLs it was read from.
specification: API Evangelist Scopes
specificationVersion: '0.1'
provider: Queensland University of Technology
providerId: qut
generated: '2026-09-01'
method: derived
source: >-
  The `scopes_supported` array of the live OpenID Provider Metadata document at
  https://esoe.qut.edu.au/auth/realms/qut/.well-known/openid-configuration, HTTP 200,
  fetched 2026-09-01 and archived at examples/qut-esoe-openid-configuration.json.
description: >-
  Every scope below is transcribed verbatim from QUT's own live discovery document. None is
  inferred and none is invented. Eleven are Keycloak / OpenID Connect standard scopes; three
  (`Service_Account`, `service_account`, `Integsvc_test_client`) are QUT-defined client scopes and
  are the only place in this profile where QUT's internal integration vocabulary is publicly
  visible. The duplicate casing of the service-account scope is QUT's, not a transcription error.
surfaces:
  - name: QUT ESOE OpenID Connect Provider
    contract: openapi/qut-esoe-openid-connect-openapi.yml
    x-operator: institution
    issuer: https://esoe.qut.edu.au/auth/realms/qut
    scopes:
      - name: openid
        standard: true
        description: Required to obtain an ID token; selects the OpenID Connect flow.
      - name: profile
        standard: true
        description: Basic profile claims — name, given_name, family_name, preferred_username.
      - name: email
        standard: true
        description: Email address claim.
      - name: phone
        standard: true
        description: Phone number claim.
      - name: address
        standard: true
        description: Address claim.
      - name: offline_access
        standard: true
        description: Issues a refresh token usable while the end user is not present.
      - name: roles
        standard: false
        description: Keycloak realm and client role claims.
      - name: basic
        standard: false
        description: Keycloak baseline claim set (sub, auth_time).
      - name: acr
        standard: false
        description: Authentication context class reference claim.
      - name: web-origins
        standard: false
        description: Keycloak scope controlling allowed CORS origins for the client.
      - name: microprofile-jwt
        standard: false
        description: MicroProfile JWT claim mapping (upn, groups).
      - name: Service_Account
        standard: false
        institution_defined: true
        description: >-
          QUT-defined client scope. Named consistently with a machine-to-machine client using the
          client_credentials grant. No public documentation of what it grants was found.
      - name: service_account
        standard: false
        institution_defined: true
        description: >-
          QUT-defined client scope, lowercase variant of the above. Both are advertised
          simultaneously by the live discovery document.
      - name: Integsvc_test_client
        standard: false
        institution_defined: true
        description: >-
          QUT-defined client scope, apparently for an integration-services test client. Recorded
          because QUT advertises it publicly; no documentation of it was found.

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/qut-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.

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