Skip to main content

High Level Software Architecture: Authenticated Interactions with OAuth 2.0—Prerequisites

  • Chat

Updated ~ minute read

Prerequisites

Before you can use Authenticated Customer Information, you are required to prepare the following:

For web implementation:

  • All authentication requests are sent over HTTPS - your web server should listen on port 443 (HTTPS).

For the embedded chat window:

  • Your webpage must contain a JavaScript method that is called by the Live Assist SDK to get the OAuth 2.0 code or JWT.

For popup chat window:

  • Your Authentication Service must expose an OpenID Connect Authorization Endpoint URL.

  • For the embedded window, a client-side developer is needed.

Configuration

Live Assist UI

For each account, define the following parameters:

  • Implicit or Code Flow

  • OAuth 2.0 Authentication Endpoint (when web external window is used)

  • JS method name and context (when LiveEngage embedded window is used in Web)

  • OAuth 2.0 Token Endpoint (when Code Flow is used)

  • OAuth 2.0 Customer JWT customer public key

  • OAuth 2.0 ClientID

  • OAuth 2.0 ClientSecret (when Code Flow is used)

To define the OAuth 2.0 authentication:

  1. From left menu select Engage > Campaign Builder. In the footnote, select Data Sources.
    datasource.png
  2. Click on INTEGTRATION tab and click Configure on Consumer Identity Providers.
    integration2.png
  3. Go to 2 Configure Identity Providers auth settings. Select your preferred authentication method or Type, and then complete the required fields.
    customer_identity_provider.png
    customer_identity_provider2.png

Brand's Authorization Service Implementation

The brand's Authorization Service must register configuration of the Live Assist authentication client:

  • LP-clientID

  • LP-clientSecret (when Code Flow is used)

  • LP Popup redirect URI (when external web window is used)

  • LP-Public key (when Implicit Flow with encryption is used)

 

Related articles