Hong Kong University of Science and Technology OAuth Scopes

OAuth 2.0 probed

Hong Kong University of Science and 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 EducationEducationResearchHong KongChinaResearch DataOpen DataIdentity FederationCourse CatalogLibrarySmart CampusAPI GatewayWayfinding
Scopes: 0 Flows: Method: probed

Scopes (0)

Hong Kong University of Science and 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 ↑
name: Hong Kong University of Science and Technology — authorization scopes
provider: Hong Kong University of Science and Technology
providerId: hkust
generated: '2026-08-30'
method: probed
source: >-
  Live probes on 2026-08-30 across every HKUST API surface found. This file records an
  ABSENCE that was checked for, not a scope catalog that exists.
summary: >-
  HKUST publishes no scope vocabulary on any surface. There is no OAuth 2.0 or OpenID
  Connect authorization server on any HKUST host probed, and therefore no scope strings to
  catalog. Authorization on the surfaces that have any is coarse-grained and binary.
surfaces:
  - surface: HKUST Path Advisor API
    x-operator: institution
    scopes: []
    model: >-
      None. Public routes are unauthenticated and unscoped; /connectors is a single
      all-or-nothing gate returning 401 with no scheme advertised.
  - surface: HKUST API Gateway (Azure API Management)
    x-operator: tenant
    scopes: []
    model: >-
      Azure API Management Products, not scopes. Authorization granularity is the Product a
      subscription key is approved against — HKUST names "IoT Sensor Data" and "Sensor
      Inventory" — and the Product catalog is not enumerable without signing in, so the
      full list cannot be verified from outside. A Product is closer to a plan than a scope
      and carries no scope string a client can request.
  - surface: HKUST Shibboleth Identity Provider
    x-operator: institution
    scopes: []
    model: >-
      SAML attribute release, not OAuth scopes. The federation-level equivalent is the
      REFEDS Research & Scholarship entity category, which HKUST's IdP carries — that
      governs which attribute bundle is released to a service provider. Per-service
      attribute release policy is not published.
    entityCategories:
      - http://refeds.org/category/research-and-scholarship
      - https://refeds.org/sirtfi
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com

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