University of Hong Kong · OAuth Scopes

University of Hong Kong OAuth Scopes

OAuth 2.0 probed

University of Hong Kong publishes 9 OAuth 2.0 scopes via the authorizationCode, clientCredentials, and deviceCode flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the University of Hong Kong API on a user’s behalf.

Tokens are issued from https://adfs.hku.hk/adfs/oauth2/token/.

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.

EducationHigher EducationUniversityHong KongIdentity FederationSingle Sign-OnResearch DataOpen AccessArtificial IntelligenceResearch Computing
Scopes: 9 Flows: authorizationCode, clientCredentials, deviceCode Method: probed

OAuth endpoints

Authorization URL
https://adfs.hku.hk/adfs/oauth2/authorize/
Token URL
https://adfs.hku.hk/adfs/oauth2/token/
Flows
authorizationCodeclientCredentialsdeviceCode

Scopes (9)

ScopeDescriptionFlows
openid Standard OpenID Connect scope — issues an ID token for the signed-in HKU account. authorizationCode, clientCredentials, deviceCode
profile Releases profile claims (unique_name, upn) about the signed-in account. authorizationCode
email Releases the account's email claim. authorizationCode
allatclaims AD FS scope that copies all claims from the underlying authentication into the issued token. authorizationCode
aza Microsoft broker scope used for primary refresh tokens on managed devices. authorizationCode
user_impersonation Allows a relying party to act on behalf of the signed-in user. authorizationCode
logon_cert Requests a logon certificate for certificate-based authentication. authorizationCode
winhello_cert Requests a Windows Hello for Business certificate. authorizationCode
vpn_cert Requests a VPN client certificate. authorizationCode

Source

OAuth Scopes

Raw ↑
generated: '2026-08-19'
method: probed
source: https://adfs.hku.hk/adfs/.well-known/openid-configuration
x-operator: institution
note: >-
  Scope strings are read verbatim from scopes_supported in HKU's live OpenID Connect discovery
  document on its own host. Descriptions are ours. These are the scopes the HKU AD FS issuer
  advertises to relying parties; HKU publishes no scope documentation of its own, and the HKU ITS
  API developer portal (developer.hku.hk) does not expose its API scopes without institutional
  sign-in.
schemes:
- name: hku-adfs-oidc
  source: https://adfs.hku.hk/adfs/.well-known/openid-configuration
  issuer: https://adfs.hku.hk/adfs
  flows:
  - flow: authorizationCode
    authorizationUrl: https://adfs.hku.hk/adfs/oauth2/authorize/
    tokenUrl: https://adfs.hku.hk/adfs/oauth2/token/
  - flow: clientCredentials
    tokenUrl: https://adfs.hku.hk/adfs/oauth2/token/
  - flow: deviceCode
    deviceAuthorizationUrl: https://adfs.hku.hk/adfs/oauth2/devicecode
    tokenUrl: https://adfs.hku.hk/adfs/oauth2/token/
scopes:
- scope: openid
  description: Standard OpenID Connect scope — issues an ID token for the signed-in HKU account.
  flows: [authorizationCode, clientCredentials, deviceCode]
  sources: [well-known/hku-adfs-openid-configuration.json]
- scope: profile
  description: Releases profile claims (unique_name, upn) about the signed-in account.
  flows: [authorizationCode]
  sources: [well-known/hku-adfs-openid-configuration.json]
- scope: email
  description: Releases the account's email claim.
  flows: [authorizationCode]
  sources: [well-known/hku-adfs-openid-configuration.json]
- scope: allatclaims
  description: AD FS scope that copies all claims from the underlying authentication into the issued token.
  flows: [authorizationCode]
  sources: [well-known/hku-adfs-openid-configuration.json]
- scope: aza
  description: Microsoft broker scope used for primary refresh tokens on managed devices.
  flows: [authorizationCode]
  sources: [well-known/hku-adfs-openid-configuration.json]
- scope: user_impersonation
  description: Allows a relying party to act on behalf of the signed-in user.
  flows: [authorizationCode]
  sources: [well-known/hku-adfs-openid-configuration.json]
- scope: logon_cert
  description: Requests a logon certificate for certificate-based authentication.
  flows: [authorizationCode]
  sources: [well-known/hku-adfs-openid-configuration.json]
- scope: winhello_cert
  description: Requests a Windows Hello for Business certificate.
  flows: [authorizationCode]
  sources: [well-known/hku-adfs-openid-configuration.json]
- scope: vpn_cert
  description: Requests a VPN client certificate.
  flows: [authorizationCode]
  sources: [well-known/hku-adfs-openid-configuration.json]
claims:
  supported: [aud, iss, iat, exp, auth_time, nonce, at_hash, c_hash, sub, upn, unique_name, pwd_url, pwd_exp, mfa_auth_time, sid, nbf]
  source: https://adfs.hku.hk/adfs/.well-known/openid-configuration
samlAttributesReleased:
  note: >-
    The Shibboleth IdP at hkafidp.hku.hk declares the attributes it releases in its SAML metadata.
    They are catalogued in vocabulary/hku-identity-attributes.yml.
  source: https://hkafidp.hku.hk/idp/shibboleth

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/hku-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 email required.

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