Using OpenID Connect
OpenID Connect in the Liberty server is implemented as an OAuth 2.0 extension. In addition to providing OpenID Connect functions, the OpenID Connect provider supports all OAuth 2.0 functions.
Subtopics
- OpenID Connect endpoint URLs
Learn about OpenID Connect endpoint URLs that are available for communicating with the OpenID Connect provider. - Getting started: Configuring an OpenID Connect Provider and Client in Liberty
This end-to-end example helps you get familiar with configuring OpenID Connect (OIDC) in Liberty since it takes you from installing Liberty through configuring OpenID Connect. The result is that client applications can verify the identity of a user by relying on authentication from an OpenID Connect Provider. - Configuring an OpenID Connect Provider in Liberty
You can configure a Liberty server to function as an OpenID Connect Provider, or authorization server, to take advantage of web single sign-on. - Configuring an OpenID Connect Client in Liberty
You can configure a Liberty server to function as an OpenID Connect Client, or Relying Party, to take advantage of web single sign-on and to use an OpenID Connect Provider as an identity provider. - Configuring OAuth 2.0 protected resources in Liberty
You can configure a Liberty server to function as OAuth 2.0 protected resource server. Configuring JSON Web Token authentication for OpenID Connect
You can configure a Liberty server to accept a JSON Web Token (JWT) token as an authentication token from a trusted authentication proxy, a trusted service client, or an OAuth authorization server.
Parent topic: Authenticating users in Liberty

File name: rwlp_using_oidc.html