TU Wien · OAuth Scopes
TU Wien OAuth Scopes
OAuth 2.0
derived
TU Wien 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 EducationEducationTechnical UniversityAustriaEuropeResearch DataResearch RepositoryOpen AccessOAI-PMHIdentity FederationResearch ComputingInvenioRDMDataCiteORCIDSAMLRIS Synergy
Scopes: 0
Flows:
Method: derived
Scopes (0)
TU Wien 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 TU Wien surface publishes a scope catalogue. The entries below are the access boundaries we could actually observe, expressed as scopes; they are OUR reading of observed behaviour, not TU Wien's declaration.
No TU Wien surface publishes a scope catalogue. The entries below are the access boundaries we could actually observe, expressed as scopes; they are OUR reading of observed behaviour, not TU Wien's declaration.
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.