> For the complete documentation index, see [llms.txt](https://docs.fortifiedid.se/access/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fortifiedid.se/access/key-components/modules/oidc.md). # OIDC Overview of OIDC and its related capabilities in Fortified ID Access. 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](/access/key-components/modules/oidc/relying-party.md) 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.	OIDC module
OIDC signing keys Configuration and behavior for OIDC signing keys, JWKS publication, and key rotation.	OIDC signing keys
Device Authorization Flow OAuth 2.0 Device Authorization Flow support in the OIDC module.	Device Authorization Flow
OpenID Configuration endpoint Returns OpenID Connect metadata.	OpenID Configuration endpoint
JWKS endpoint Returns the JSON Web Key Set containing the public keys used to verify token signatures.	JWKS endpoint
Authorization endpoint This is the starting point for OpenID Connect flows.	Authorization endpoint
Token endpoint Overview of Token endpoint and its related capabilities in Fortified ID Access.	Token endpoint
User info endpoint Returns information about the authenticated user.	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.	Introspection endpoint
End session endpoint Logout endpoint to terminate the user session.	End session endpoint
Relying Party Configuration and usage guidance for Relying Party in Fortified ID Access.	Relying Party

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.fortifiedid.se/access/key-components/modules/oidc.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.