OAuth 2.0 and OpenID Connect (OIDC) overview

OAuth 2.0 is an authorization framework that enables target applications (so-called OAuth 2.0 Clients) to securely obtain access to protected HTTP resources (such as user information) on behalf of a user. The obvious way to achieve this goal would be for the user to share her credentials (e.g. her password) with the target application. As sharing passwords has many drawbacks, OAuth 2.0 solves this problem without requiring the user to share credentials.

OpenID Connect 1.0 adds an identity layer to the OAuth 2.0 protocol, allows clients to verify the user's identity information and usually save a few HTTP roundtrips.

Supported features

The following table lists the OAuth/OIDC feature set supported by Airlock IAM.

Features

OAuth 2.0 Authorization Server (AS)

OAuth 2.0 Client

OAuth 2.0

OAuth 2.0 Authorization Code Grant*

Icon - ON
Icon - ON

OAuth 2.0 Client Credentials Grant*

Icon - ON

OAuth 2.0 Token Exchange Grant*

Icon - ON

OAuth 2.0 Implicit Grant
(officially no longer recommended for use by the OAuth Working Group)

OAuth 2.0 Token Introspection

Icon - ON

OAuth 2.0 Token Revocation

Icon - ON

OAuth 2.0 Dynamic Client Registration

Icon - ON

Pushed Authorization Request (PAR)

Icon - ON

OAuth 2.0 Authorization Server Metadata Endpoint

Icon - ON
Icon - ON

OIDC

OpenID Connect Authorization Code Flow

Icon - ON
Icon - ON

OpenID Connect Hybrid Flow

Icon - ON

OpenID Connect Implicit Flow

OpenID Connect Token Introspection

Icon - ON

OpenID Connect Token Revocation

Icon - ON

OpenID Connect Discovery

Icon - ON
Icon - ON

OAuth 2.0 Dynamic Client Registration

Icon - ON

OpenID Connection Session Management

Icon - ON

OpenID Connect UserInfo Endpoint

Icon - ON
Icon - ON

OpenID Connect RP-initiated logout (as RP)

Icon - ON

Account Linking

Icon - ON

Automated Account Registration (Social Registration)

Icon - ON

Pushed Authorization Request (PAR)

Icon - ON
*

Implemented grant type.