PeopleSoft · OAuth Scopes
PeopleSoft OAuth Scopes
OAuth 2.0
derived
PeopleSoft 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.
Tokens are issued from https://{hostname}:{port}/psft/oauth/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.
Campus SolutionsCRMEnterprise SoftwareERPFinancial ManagementHCMSupply Chain Management
Scopes: 0
Flows: authorizationCode
Method: derived
OAuth endpoints
Authorization URL
https://{hostname}:{port}/psft/oauth/authorize
https://{hostname}:{port}/psft/oauth/authorize
Token URL
https://{hostname}:{port}/psft/oauth/token
https://{hostname}:{port}/psft/oauth/token
Flows
authorizationCode
authorizationCode
Scopes (0)
PeopleSoft 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.
PeopleSoft OAuth 2.0 (PeopleTools 8.58+) publishes no scope catalog; authorization is enforced by PeopleSoft permission lists and roles tied to the user ID in the token's sub claim, with any scopes defined per deployment in the external identity provider (see https://docs.oracle.com/cd/F30998_01/pt858pbr2/eng/pt/tsec/concept_UnderstandingOAuth2_0.html).
PeopleSoft OAuth 2.0 (PeopleTools 8.58+) publishes no scope catalog; authorization is enforced by PeopleSoft permission lists and roles tied to the user ID in the token's sub claim, with any scopes defined per deployment in the external identity provider (see https://docs.oracle.com/cd/F30998_01/pt858pbr2/eng/pt/tsec/concept_UnderstandingOAuth2_0.html).
📄 Provider scope reference: https://docs.oracle.com/cd/F30998_01/pt858pbr2/eng/pt/tsec/concept_UnderstandingOAuth2_0.html