Home
OpenID Implementation
This document contains technical information for publishers and integrators about OpenID Connect (OIDC) protocol.
Overview of OpenID CONNECT
The OpenID Connect (OIDC) protocol is an extension of OAuth 2.0 for use as an authentication protocol.
Protocol Flow
The steps of the OIDC authorization flow are as follows:

OpenID Implementation
This document contains technical information for publishers and integrators about OpenID Connect (OIDC) protocol.
- Overview of CONNECT
  CONNECT is an Identity Management as a Service (IDaaS) platform created and managed by Wiley Partner Solutions that enables publishers to securely sign in users to their applications, using the OpenID Connect (OIDC) protocol.
- Overview of OpenID CONNECT
  The OpenID Connect (OIDC) protocol is an extension of OAuth 2.0 for use as an authentication protocol.
  - Protocol Flow
    The steps of the OIDC authorization flow are as follows:
- Client Application Configuration
  A client application represents an application (typically a web application) of a publisher that provides services to authenticated users. Each application always belongs to one CONNECT tenant (customer). Each customer can have multiple applications.
- Metadata Document
  The OpenID Connect service is a metadata document that contains most of the information required for a client application to perform the authorization flow. This includes information such as the URLs to use and the location of the service's public signing keys.
- The Authorization Request
  When a web application needs to authenticate a user, it must direct the browser to the URL of the authorization_endpoint, specified in the application metadata. This request is also referred to as the authorization request.
- The id_token
  The id_token can be provided either in JSON format or as a signed JWT (configurable on the CONNECT side according to the client application requirements) and includes basic user profile data that allows the authentication of a user on the client application.
- Automatic Login
  The user authentication status on CONNECT can be checked by an application by issuing a "silent" authorization request.
- Retrieving User Data
  Some applications not only need to sign the user in, but also access a web service on behalf of that user using OAuth. An example of this is a service that provides additional user data than those included in the id_token.
- Scopes
- Logout
- Back Channels APIs

Protocol Flow

The steps of the OIDC authorization flow are as follows:

The user clicks login on the publisher website.
Upon the reception of the login request from the user, the web server initiates an OIDC authorization request by constructing a URL and redirecting the user to this URL through a browser redirect.
The ODIC Server initiates user authentication by displaying the user a login interface.
The user submits their credentials.
The credentials are validated and the user is authenticated. The OIDC Server redirects the user back to the web server, through a browser redirect, providing an id_token and a code.
The web server retrieves the user information from the id_token, authenticates the user, and creates a session.
The user is authenticated to the web server.
The web server exchanges the code received from step 6 with an access token that will allow the retrieval of additional user profile data for this user.
The web server uses the access token to retrieve more user profile data.
The OIDC server validates the access token and provides the web server with the requested profile data.