16 docs tagged with "oidc"

In OpenID Connect (OIDC), Standard Claims (like sub, email, name) and Custom Claims are attributes directly asserted and digitally signed by the primary OpenID Provider (OP).

OpenID Connect Core 1.0 incorporating errata set 2 - AuthRequest

OpenID Connect Core 1.0 incorporating errata set 2 - CodeFlowAuth

OpenID Connect Core 1.0 incorporating errata set 2 - 5.1 Standard Claims

OpenID Connect Core 1.0 incorporating errata set 2 - ID Token

OpenID Connect Core 1.0 incorporating errata set 2 - 4. Initiating Login from a Third Party

OpenID Connect Core 1.0 incorporating errata set 2 - Offline Access

Category | Endpoint | Request | Description

Modern digital applications demand secure, and user authentication without friction.

In OpenID Connect, the sub (subject) claim in the ID Token acts as the unique identifier for the End-User.

The Token Endpoint is a crucial part of the OIDC and OAuth 2.0 flows. Unlike the Authorization Endpoint, which is accessed through the user's browser (front-channel), the Token Endpoint is designed for secure, direct, server-to-server communication (back-channel).

The UserInfo Endpoint is a protected resource hosted by the OpenID Provider (OP). Its purpose is to return claims about the authenticated user, such as their name, email address, or profile picture.

OpenID Connect Core 1.0 incorporating errata set 2 - Passing Request Parameters as JWTs

OpenID Connect Core 1.0 - Using Refresh Tokens

Scopes in OpenID Connect are values used during authentication to specify which user data a client application wants to access.

OpenID Connect Core 1.0 incorporating errata set 2 - Self-Issued OpenID Provider