Skip to main content

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

Configuring Digital Messaging channel security

Updated on June 1, 2023

To enable users to chat on various messaging platforms using Pega Intelligent Virtual Assistant™ (IVA), configure the security settings for your Digital Messaging channel. When you define the security settings for the system, you can access Digital Messaging Manager for your channel. For example, you can then set up Apple Business Chat, Facebook Messenger, WhatsApp Messenger, and Web Messaging as chatbot messaging platforms for your application.

Before you begin:
  • Verify that your application meets the requirements to access Digital Messaging Manager. The following are the minimum Pega Customer Service and Pega Platform versions required:
    • Pega Customer Service version 8.4.4 with Pega Platform version 8.4.5.
    • Pega Customer Service version 8.5.2 with Pega Platform version 8.5.4.
    • Pega Customer Service version 8.6 with Pega Platform version 8.6.
  • Define a publicly accessible secured URL for the environment, or configure the system to allow communication with Digital Messaging Service.
  • Obtain the security settings for your Digital Messaging channel, including the Manager ID and the Manager Key values for Digital Messaging Manager, by contacting Pega Support. For more information, go to Pega Support.
  • Ensure that you request a separate set of credentials for each environment that you maintain.
  • If your Pega Platform is installed on premises or has internal access only, perform additional configuration for your environment so that your system can communicate with Digital Messaging Service. For more information, see Configuring on-premises or internal access only environments for Digital Messaging access.

Digital Messaging requires a separate set of Manager ID and Manager Key credentials for each instance of Pega Platform. If you have multiple instances of Pega Platform, for example, for development, staging, and production purposes, specify the number of instances in your request to Pega Support, so that you receive a unique set of credentials for each instance.

  1. Switch to Dev Studio.
  2. In the header of Dev Studio, click the name of the application, and then click Definition.
  3. In the application rule, click the Security tab.
  4. In the Digital Messaging security section, in the Manager ID field, enter the identifier for Digital Messaging Manager.
  5. In the Manager Key field, enter the key for Digital Messaging Manager.
  6. In the Authentication method section, click API Key or JWT.
    You will receive the configured authentication method for your system with your identifiers when Pega provisions Digital Messaging Service Manager ID and Manager Key credentials for your environment.
  7. Click Save.
  8. Switch back to App Studio.
What to do next: Set up a Digital Messaging channel for messaging platforms such as Apple Messages for Business or Facebook Messenger by adding messaging accounts in Digital Messaging Manager. For more information, see Creating a Digital Messaging channel. Note: Messaging accounts that you set up for your channel cannot be duplicated within the same application or across other applications. If you reuse a messaging account, the system displays already connected error in the Digital Messaging Manager. For example, as best practice, when moving your application from a staging to a production environment, ensure that you first delete the messaging account connection in the Digital Messaging Manager for your staging environment, before you attempt to connect the same messaging account to a production environment.
  • Previous topic Best practices when using an IVA for WhatsApp
  • Next topic Configuring on-premises or internal access only environments for Digital Messaging access

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us