Home
OpenID Implementation
This document contains technical information for publishers and integrators about OpenID Connect (OIDC) protocol.
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.
Getting an Access Token
The code received in the successful response of the authorization can be exchanged for an access token, with a token request to the token_endpoint specified in the metadata document.
Successful Response and Parameters

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.
- 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.
  - Getting an Authorization Code
    To acquire an access token, the authorization request must include code in the response type parameter.
  - Getting an Access Token
    The code received in the successful response of the authorization can be exchanged for an access token, with a token request to the token_endpoint specified in the metadata document.
  - Getting User Data from the User Info Endpoint
    The access token can be used to retrieve user data from the user-info endpoint.
- Scopes
- Logout
- Back Channels APIs

Successful Response and Parameters

A successful response can be as follows:

{ 
  "access_token":"yJd8Hu2VlYkwdx43_U3g7BmQYv9pEaDJtnI2W_...", 
  "refresh_token":"_WPSJB-Dm3mQVx3LcK_w_...", 
  "id_token":"eyJraWQiOiJqd3QiLCJhbGciOiJSUzUxMiJ9.eyJzdWzFiMDk5MC1lNWRhLTQ..." 
} 
content-type : "application/json;

It contains the following parameters:

Parameter Name	Description
`access_token`	The access token used by the client to authenticate in user info requests.
`refresh_token`	The token used to obtain a new access token without re-authenticating the user, extending the session's validity.
`scope`	A space-separated list of scopes. It must include the openid scope.
`id_token`	A JSON Web Token (JWT) contains user identity information, including claims about the authenticated user. It is issued by the authorization server and used by the client to verify the user’s authentication.