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

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. In Live Assist, select Manage campaigns and engagements.In the footnote, select Data Sources.
2. In the Connectors area,next to the authentication server, click Configure.
   The Authentication Server page is displayed.
   
   
   
   
   
3. From the dropdown menu, select your preferred authentication method, and then complete the required fields.

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)