University of Michigan-Ann Arbor · OAuth Scopes

University of Michigan-Ann Arbor OAuth Scopes

OAuth 2.0 probed

University of Michigan-Ann Arbor 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 EducationEducationPublic Research UniversityUnited StatesMichiganBig TenAssociation of American UniversitiesResearch DataInstitutional RepositoryIdentity FederationOAI-PMHLibraryResearch Computing

Scopes: 0 Flows: Method: probed

Scopes (0)

University of Michigan-Ann Arbor 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 scope model exists to record, and that is a finding rather than a gap in the research. The one U-M contract this repo describes — the Deep Blue Documents OAI-PMH endpoint — is unauthenticated by protocol design: OAI-PMH 2.0 has no authorization layer, the endpoint answered every verb anonymously, and there is therefore nothing to scope. The enterprise estate that WOULD carry scopes, the ITS API Directory on Apigee X, is unreachable without a U-M uniqname, Duo two-factor and campus-network/VPN presence, so no scope catalog could be read. No scopes have been invented to fill the slot.

📄 Provider scope reference:

Source

OAuth Scopes

---
name: University of Michigan-Ann Arbor — Authorization Scopes
generated: '2026-08-19'
method: probed
source: >-
  Live probe of the one institution-operated contract in this repo
  (backend.production.deepblue-documents.lib.umich.edu OAI-PMH) plus attempted probes of the
  gated ITS API Directory, 2026-08-19.
operator: institution
scopes: []
note: >-
  No scope model exists to record, and that is a finding rather than a gap in the research.
  The one U-M contract this repo describes — the Deep Blue Documents OAI-PMH endpoint — is
  unauthenticated by protocol design: OAI-PMH 2.0 has no authorization layer, the endpoint
  answered every verb anonymously, and there is therefore nothing to scope. The enterprise
  estate that WOULD carry scopes, the ITS API Directory on Apigee X, is unreachable without a
  U-M uniqname, Duo two-factor and campus-network/VPN presence, so no scope catalog could be
  read. No scopes have been invented to fill the slot.
authorization_boundaries_observed:
  - boundary: OAI-PMH set restriction
    mechanism: '?set=<setSpec>'
    description: >-
      The only access-partitioning mechanism on the open surface. 726 sets are advertised
      (com_2027.42_* communities, col_2027.42_* collections). This partitions WHAT is
      harvested, not WHO may harvest — every set is readable anonymously.
  - boundary: ITS API Directory subscription
    mechanism: per-API subscription behind U-M SSO
    description: >-
      Consumers subscribe per API in the Apigee portal and receive a key/secret pair exchanged
      at a token endpoint. Whether Apigee product entitlements are surfaced as OAuth scopes
      could not be determined without an account.
    readable: false