Peking University OAuth Scopes

OAuth 2.0 probed

Peking 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.

UniversityHigher EducationEducationChinaPublic Research UniversityC9 LeagueResearch RepositoryIdentity FederationResearch DataOpen DataResearch ComputingOAI-PMH

Scopes: 0 Flows: Method: probed

Scopes (0)

Peking 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.

No OAuth scope vocabulary is published by Peking University. The IAAA unified authentication service exposes an OAuth authorization page (HTTP 200) but no discovery document — /.well-known/openid-configuration was not served on any PKU host probed on 2026-08-19 — and client registration is an internal, approval-gated process. The federated surface uses SAML attribute release, not OAuth scopes; the attribute authority is declared in the IdP metadata and its released attribute set is negotiated per service provider through CARSI rather than published. Nothing is asserted here that was not observed. This file records an absence.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-19'
method: probed
source: https://iaaa.pku.edu.cn/iaaa/oauth.jsp
x-operator: institution
note: >-
  No OAuth scope vocabulary is published by Peking University. The IAAA unified
  authentication service exposes an OAuth authorization page (HTTP 200) but no
  discovery document — /.well-known/openid-configuration was not served on any PKU
  host probed on 2026-08-19 — and client registration is an internal, approval-gated
  process. The federated surface uses SAML attribute release, not OAuth scopes;
  the attribute authority is declared in the IdP metadata and its released attribute
  set is negotiated per service provider through CARSI rather than published.
  Nothing is asserted here that was not observed. This file records an absence.
schemes: []
scopes: []
saml_attribute_release:
  documented_publicly: false
  attribute_authority: https://idp.pku.edu.cn:8443/idp/profile/SAML2/SOAP/AttributeQuery
  scope: pku.edu.cn
  note: >-
    The IdP declares an AttributeAuthorityDescriptor and a shibmd:Scope of pku.edu.cn,
    so attribute release exists and is machine-declared; the released attribute names
    themselves are not published on a public surface.

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

GitHub Google LinkedIn

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