OIDC

This section describes the different ways that Fortified ID Access supports OIDC. Click on any of the subcategories to read more depending on what you want to do.

If you are configuring Fortified ID Access as an OIDC OpenID Provider (OP), the Relying Party section also covers per-application settings such as token claims, pipe integration and app-specific authorization.

OpenID Connect capabilities in Fortified ID Access

Explore this section

OIDC module Acts as an OpenID Connect Provider.	Open OIDC module
OIDC signing keys Configuration and behavior for OIDC signing keys, JWKS publication, and key rotation.	Open OIDC signing keys
Device Authorization Flow OAuth 2.0 Device Authorization Flow support in the OIDC module.	Open Device Authorization Flow
OpenID Configuration endpoint Returns OpenID Connect metadata.	Open OpenID Configuration endpoint
JWKS endpoint Returns the JSON Web Key Set containing the public keys used to verify token signatures.	Open JWKS endpoint
Authorization endpoint This is the starting point for OpenID Connect flows.	Open Authorization endpoint
Token endpoint Overview of Token endpoint and its related capabilities in Fortified ID Access.	Open Token endpoint
User info endpoint Returns information about the authenticated user.	Open User info endpoint
Introspection endpoint The introspection endpoint provides a way to validate mainly access tokens (active/inactive) and retrieve their associated claims, such as scopes, subject, expiration time, and client information.	Open Introspection endpoint
End session endpoint Logout endpoint to terminate the user session.	Open End session endpoint
Relying Party Configuration and usage guidance for Relying Party in Fortified ID Access.	Open Relying Party

In this section

• OIDC module
• OIDC signing keys
• Device Authorization Flow
• OpenID Configuration endpoint
• JWKS endpoint
• Authorization endpoint
• Token endpoint
• User info endpoint
• Introspection endpoint
• End session endpoint
• Relying Party