Red Hat Satellite · OAuth Scopes
Red Hat Satellite OAuth Scopes
OAuth 2.0
derived
Red Hat Satellite 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.
Configuration ManagementLifecycle ManagementPatch ManagementSubscription ManagementSystems Management
Scopes: 0
Flows: implicit
Method: derived
OAuth endpoints
Authorization URL
https://satellite.example.com/users/extlogin
https://satellite.example.com/users/extlogin
Flows
implicit
implicit
Scopes (0)
Red Hat Satellite 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.
Red Hat Satellite does not use OAuth 2.0 scopes; the REST API authenticates via HTTP basic auth, Personal Access Tokens, SSO sessions, or legacy 1-legged OAuth 1.0a, with authorization governed by Foreman role-based permissions (roles and filters) rather than scopes (https://docs.redhat.com/en/documentation/red_hat_satellite/6.11/html/api_guide/chap-red_hat_satellite-api_guide-authenticating_api_calls).
Red Hat Satellite does not use OAuth 2.0 scopes; the REST API authenticates via HTTP basic auth, Personal Access Tokens, SSO sessions, or legacy 1-legged OAuth 1.0a, with authorization governed by Foreman role-based permissions (roles and filters) rather than scopes (https://docs.redhat.com/en/documentation/red_hat_satellite/6.11/html/api_guide/chap-red_hat_satellite-api_guide-authenticating_api_calls).
📄 Provider scope reference: https://docs.redhat.com/en/documentation/red_hat_satellite/6.11/html/api_guide/chap-red_hat_satellite-api_guide-authenticating_api_calls