started · updated
OpenID Connect and OpenID Federation enhance OAuth identity layers
OpenID Connect (OIDC) serves as a standardized identity layer built on top of the OAuth 2.0 protocol. While OAuth 2.0 provides delegated authorization, OIDC enables applications to verify user identity through the use of ID tokens. These tokens contain specific claims, such as the issuer and subject identifier, which allow applications to confirm who has signed in.
To address the administrative complexity of manual application onboarding across multiple identity providers, OpenID Federation introduces a trust anchor (TA). This mechanism allows Relying Parties (RP) and OpenID Providers (OP) to establish trust through signed entity statements and trust chains. This enables automatic metadata validation and registration.
In the Java ecosystem, the open-source security library pac4j has implemented support for OpenID Federation as a Relying Party. Developers are advised to use the combination of the token’s issuer and subject claims to identify users rather than relying on email addresses, which can change, and to always validate ID tokens using maintained libraries.
Entities
Google · OAuth · OpenID Connect · pac4j