Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Setting up the Voice AI authentication profile

Updated on December 3, 2021

Configure your OAuth 2.0 authentication profile to enable communication between Pega Platform and the Voice AI services in your Pega Customer Service application.

Pega Customer Service Implementation Guide

Note: This section focuses on the configuration parameters that you use for the Voice AI authentication profile. For general instructions on how to configure an OAuth 2.0 authentication profile, see Configuring an OAuth 2.0 authentication profile.
  1. In the navigation pane of Dev Studio, click RecordsSecurityAuthentication Profile.
  2. Configure the VoiceAIAccessToken authentication profile:
    PropertyValue
    OAuth 2.0 ProviderSelect Custom.
    Grant typeSelect Client credentials.
    Client identifierEnter the client ID that Pega provides during onboarding.
    Client secretEnter the client secret that Pega provides during onboarding.
    ScopeEnter vas/speech.
    Access token endpointEnter the authentication URL that Pega provides during onboarding, in the following format:

    authentication_url/oauth2/token

    Note: Ensure that the access token endpoint has no parameters.
    Authentication schemeSelect Client secret.
    MethodSelect POST.
    Send access token asSelect Authorization header.
    Lowest available SSL/TLS versionSelect TLSv1.2.
  3. Save the configuration.

Tags

Pega Customer Service 8.7 Pega Customer Service for Communications 8.7 Pega Customer Service for Financial Services 8.7 Pega Customer Service for Healthcare 8.7 Pega Customer Service for Insurance 8.7

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us