Brands can provide LivePerson's Conversational Builder Bots a consumer (OAuth 2.0) access token. This token can later be used to access the brand's APIs on behalf of the consumer.
By configuring Consumer Authentication credentials, an authentication challange is sent to the consumer. Once autnentication is completed, an access token is obtained and sent to the bot. This “delegates” access to the bot, so it can make the API calls.
This can be done in order to accomplish many business and operational use cases on which Bots integrates with brand's APIs such as:

  • To enrich conversation by retrieving information about the consumer.
  • To perform an operation on behalf of the consumer

The Flow

You can create a Consumer Authentication credential and use it in API integrations when you require the bot to make API calls on behalf of the consumer. With this credential, the consumer receives an authentication link, uses it to authenticate, and obtains a token that is sent to the bot. This “delegates” access to the bot, so it can make the API calls. The general flow is this:

  1. In the bot, the Integration interaction is triggered in the dialog.
  2. The bot sends an authentication URL (a plain link) to the consumer.

  3. The consumer clicks the link, is directed to the authentication URL (e.g., a login page), and authenticates, thereby obtaining a token.
  4. The token is sent to the bot.
  5. The bot runs the integration (with the token) and responds with a result.

Implementation Steps

1. Configure Consumer Authentication credentials

  1. In the Bot Accounts application, select the name of the organization for which to create the credential.
  2. Click Credentials in the upper-left corner.
  3. Click Add Credentials in the upper-right corner.
  4. In the Add Credentials dialog box, specify the following:
    • Name: Enter a descriptive name.
    • Authentication Type: Select "Consumer Authentication."
  5. Click Next.
  6. In the Add Credentials dialog box, specify the following:
    • Authentication URL: Enter the authentication endpoint to be sent to the consumer in order to obtain an access token that is sent to the bot. The URL is provided by the resource provider; see their documentation for this information.
      • Note: The authentication URL must include the following query params:
        • client_id={PROVIDE THE CLIENT ID}
        • response_type=code
        • redirectedCode={PROVIDE THE REDIRECT URI}
        • scope={PROVIDE THE SCOPE}

Authentication URL Example 

  1. Click Save.

2. Integrate with Brand API

To use a defined Consumer Authentication credential in a bot, go into the bot and add an API integration. When you do, select the Consumer Authentication credential that you created and provide the endpoint.

Then, add the provided access as an authorization header to the API integration.
In request headers, add authozion header:
key = Authorization
value = Bearer {$botContext.cidp_accessToken}

3. Configure Delegated Access Provider

Follow this configuration guide: Consumer Delegation

4. Configutre Dialog
Dialog should inclde an API integration and consumer verification delegation button.
Note: The API integration must be included and ordered in the dialog flow before the consumer verification dialog button.

4.1 add integration

Add the integration that requires the consumer access token and make sure the following are applied:

  • "Next action" should be using custom rules - one for failure and the other for success. In case of API failure, route the dialog to the connsumer delegation link.
  • The following code should be included as a pre-process code for the Integration API.
var cidp_accessToken = botContext.getWebViewVariable('cidp_accessToken');

if(cidp_accessToken) {

4.2. Add Consumer Delegation Link to the Conversation Flow

Before accessing the protected integrated API, we need to prompt user to verify his identity. This will be done in the conversation dialog by adding an interactive button to the conversation.
The following paraeter should be define in the inetartive button/questions:
Button Label = Login
Action Type = Web URL
Webview = Full
Target = New Window
Callback = {$botContext.external_auth_url}