Series: Web chat to web messaging migration guide

Enable authenticated web messaging

Prerequisites
  • Genesys Cloud CX 2, Genesys Cloud CX 3, Genesys Cloud CX 1 Digital Add-on II, Genesys Cloud CX 2 Digital, or Genesys Cloud CX 3 Digital license
  • Web Deployments > Configurations > All permission
  • Web Deployments > Deployments > All permission
  • An inbound messaging flow

Authenticated web messaging allows only authenticated users to start a web messaging session with your agents. These users must log in to your website before they can send a web message.

Note: Genesys relies on OpenID Connect as an open standard for integrating into identity providers and authentication services.

Before you begin

Review the following articles:

    Steps to take

    1. Create or configure an authentication server (an OpenID provider).
    2. Create an OpenID Connect Messenger Configuration integration. When you configure credentials for this integration, use the client-id and client-secret.
    3. In your Messenger configuration, enable Authentication. In the Authentication area of the configuration, select the OpenID Connect Messenger Configuration integration. 
    4. Create and save a Messenger deployment. Assign this Messenger configuration to your deployment.  
    5. Set the Messenger deployment to Active. Copy the code snippet from this deployment to the website pages where you want Messenger to appear, or use a Tag Manager tool to deploy it.

    For more information, see these Developer center articles: Authenticated web messaging and Auth plugin and AuthProvider plugin in Commands and Events.

    Web chat to web messaging migration and impact :Previous Suggested Article Next Suggested Article: Migrate web chat flows to message flows