Home
OpenID Implementation
This document contains technical information for publishers and integrators about OpenID Connect (OIDC) protocol.
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.

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.
  - id_token Attributes
    The following attributes are included to the id_token:
  - Token Validation
- 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

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.

The id_token can be as follows:

{ 
  "sub": "5f188124-a5cb-48de-9e07-17a60f2c2101", 
  "iss": "https://customer.scienceconnect.io", 
  "type": "registered", 
  "nonce": "4013387ef6cb75ae94687464d049dd9b", 
  "sid": "b8d484b3-2555-4041-9966-fdca228ed9c8", 
  "email": "[email protected]", 
  "email_verified": true, 
  "address": { 
    "country": " Listenbourg" 
  }, 
  "emails": [ 
    { 
      "verified": true, 
      "value": "[email protected]" 
    }, 
    { 
      "verified": true, 
      "value": "[email protected]" 
    } 
  ], 
  "aud": "client_id", 
  "user_interaction": "login", 
  "name": "John Doe", 
  "family_name": "Doe", 
  "given_name": "John", 
  "middle_name": "Michael", 
  "exp": 1669997471, 
  "iat": 1667405471 
}