Wuhan University · OAuth Scopes

Wuhan University OAuth Scopes

OAuth 2.0 searched

Wuhan University 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.

EducationHigher EducationUniversityResearchChinaIdentity FederationSingle Sign-OnResearch DataGNSSLibraryOpen-Source
Scopes: 0 Flows: Method: searched

Scopes (0)

Wuhan University 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

wuhan-scopes.yml Raw ↑
specification: API Evangelist Scopes
specificationVersion: '0.1'
provider: Wuhan University
providerId: wuhan
generated: '2026-09-01'
method: searched
source: >-
  scopes_supported and claims_supported read verbatim from the OpenID Connect discovery document
  Wuhan University publishes at
  https://cas.whu.edu.cn/authserver/oidc/.well-known/openid-configuration (HTTP 200,
  application/json;charset=UTF-8, 1,340 bytes, fetched 2026-09-01, archived at
  authentication/wuhan-cas-oidc-openid-configuration.json). Nothing in this file is inferred or
  generated -- every value below appears in that document.
description: >-
  The only scope vocabulary Wuhan University publishes anywhere. These are the standard OpenID
  Connect 1.0 scopes as emitted by the Wisedu CAS authorization server at cas.whu.edu.cn; there
  are no institution-specific scopes, no resource scopes, and no data-API scopes, because there
  is no institution-operated data API to scope. Scopes here govern who may read a WHU identity,
  not what a client may do with WHU information.

x-operator: institution
x-operator-basis: >-
  Served from cas.whu.edu.cn (115.156.123.25, netname WHR-CERNET, Wuhan Regional Network). The
  scope SET is the OIDC standard as shipped by the supplier's product, not a WHU design -- the
  deployment is institution-operated, the vocabulary is the specification's.

issuer: https://cas.whu.edu.cn/authserver/oidc/

scopes:
- name: openid
  standard: OpenID Connect Core 1.0
  description: Required to request an ID token; identifies the request as an OIDC authentication.
- name: profile
  standard: OpenID Connect Core 1.0
  description: >-
    Releases the profile claim set the server advertises: name, preferred_username, family_name,
    given_name, middle_name, nickname, picture, website, gender, birthdate, zoneinfo, locale,
    updated_at.
- name: email
  standard: OpenID Connect Core 1.0
  description: Releases email and email_verified.
- name: address
  standard: OpenID Connect Core 1.0
  description: Releases the address claim.
- name: phone
  standard: OpenID Connect Core 1.0
  description: Releases phone_number and phone_number_verified.
- name: offline_access
  standard: OpenID Connect Core 1.0
  description: Requests a refresh token for use when the subject is not present.

claims_supported:
- sub
- name
- preferred_username
- family_name
- given_name
- middle_name
- profile
- picture
- nickname
- website
- zoneinfo
- locale
- updated_at
- birthdate
- email
- email_verified
- phone_number
- phone_number_verified
- address
- gender

observations:
- >-
  claims_supported lists given_name twice. A duplicate entry in a published discovery document
  is a small correctness defect in the artifact, and it is reproduced faithfully above minus the
  duplicate.
- >-
  No institution-defined scope exists. Every scope is the OIDC standard set, which is the
  expected shape for a campus SSO and the expected absence for an institution that operates no
  public API.

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