Securian Financial Group · OAuth Scopes
Securian Financial Group OAuth Scopes
OAuth 2.0
probed
Securian Financial Group 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.
Fortune 1000Financial ServicesInsuranceLife InsuranceAnnuitiesRetirementGroup BenefitsEmployee Benefits
Scopes: 0
Flows:
Method: probed
Scopes (0)
Securian Financial Group 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.
scopes_supported read verbatim from Securian's published OpenID Connect discovery document. There is no public scopes/permissions reference page to enrich these with — the descriptions below for the four standard OIDC scopes are the OpenID Connect Core 1.0 definitions; the two non-standard scopes (edit, admin) are advertised by the server with no published description, and are recorded here without one rather than guessed at.
scopes_supported read verbatim from Securian's published OpenID Connect discovery document. There is no public scopes/permissions reference page to enrich these with — the descriptions below for the four standard OIDC scopes are the OpenID Connect Core 1.0 definitions; the two non-standard scopes (edit, admin) are advertised by the server with no published description, and are recorded here without one rather than guessed at.
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.