As of Friday October 16th, access to restricted content on this site now requires you to log in with your Genesys account. If you don't have an account, you can request one at these locations: Request MyPartner Portal Account or Request My Support Account.

Provisioning Genesys Engage Hybrid Integrations

From Genesys Documentation
Jump to: navigation, search

This article describes the essential provisioning steps to enable a hybrid integration between Genesys Engage On-Premises deployments and Genesys Cloud services. This enables you to access many of the great Genesys Cloud Services in your On-Premises deployments.

Supported Services

The following Genesys Cloud services are supported and have supplementary documentation:

About Provisioning

Before proceeding with the information in this article you should consult with the Genesys Professional Services team that you are working with to obtain the information needed to complete the provisioning.

To support the different authentication mechanisms in Genesys Cloud Integration, you must create a transaction object in Genesys Engage Configuration Server. Genesys Engage On-Premises Services, Components, and UIs will use this information to authenticate with the Genesys Cloud Common Services and UIs.

Use Genesys Administrator Extension to manually create all of the Genesys Cloud Common Service–related configuration information in Configuration Server at the Tenant level.

After you purchase a common cloud service, a Genesys Cloud Organization is created for you and you will receive a welcome email to activate your admin accounts with Genesys Cloud.

A Genesys Cloud organization has been created for you to support your hybrid integration. This organization has been provisioned with the following:

  • The base functionality required for your Common Cloud integration.
  • An Admin console that you may use to configure your Common Cloud integration.
  • A user with the Genesys Cloud Admin role, which includes default admin permissions as well as Single Sign-On and any integration-specific permissions.
  • A default AI Agent role (if required by your integration) that provides agent access to AI services, such as Genesys Predictive Engagement.

As an administrator, you may access your Genesys Cloud organization by logging in at (or a region specific login URL; The Genesys Cloud welcome email directs you to the appropriate application URL for your region) with the credentials you set when you activate your Genesys Cloud account from the welcome email you received.

Upon activation of your Genesys Cloud account, perform the steps in the Genesys Cloud Provisioning Steps section below using the Genesys Cloud Admin UI or the Genesys Cloud API.

With the credentials provided in the Welcome email, you can log in to the Genesys Cloud Admin UI for your region to perform the provisioning steps described in the next section.

  1. In the Genesys Cloud Admin UI, select Account Settings.
  2. Open Organization Settings.
  3. In the Organization Details tab, open Advanced.
  4. Copy the Company Name, Short Name, and Organization ID — you will need these values to complete your account configuration in the Genesys Engage On Premises: Transaction object for hybrid integrations section. For example:
    Hybrid Organization Name And ID.png

The following diagram provides an overview of how Genesys Engage utilizes Genesys Cloud services such as Genesys Predictive Engagement:

Genesys Cloud Provisioning Steps

For each Genesys Cloud Organization that is created for each of your tenants (for environments with multiple Genesys Engage tenants), perform the following steps using the Genesys Cloud Admin UI or the Genesys Cloud API.

  1. For each Genesys Engage Service that uses a common service you must create an OAuth client to allow for better control and monitoring of the components using the Genesys Cloud Services and for different rate limiting per client. (This does not mean that if you have n number of components on premises that are associated with one another, they cannot share a given client id.)

    Genesys recommends that you consult architecture before performing this step.

    Login to your Genesys Cloud Region, then follow these steps:

    1. Create a Client Credential OAuth Client that is to based on the specific services you are using, such as the Pacing Service. It is required to create the Genesys Cloud Genesys Engage Identity Provider (IDP). In your Genesys Cloud Region, create a Client Credential Grant. Open Integrations, select OAuth, and enter PureEnagage Client Credentials as the App name in the Client Details tab. Select the Client Credentials grant type.
      Hybrid Client Credential OAuth Grant.png
      In the Roles tab, assign the Admin role and set the division as Home.
      Hybrid Client Credentials Role Assignment.png
      As necessary, for each on-premises service, like the "Agent Pacing Service" (ewt), create OAuth Client Credentials grants:

      For more information about Permissions for Genesys Predictive Engagement, see the Altocloud permissions overview.

    2. Create a SAML2 Bearer OAuth Client for the client, such as Genesys Engage Workspace Desktop Edition, that needs to send a SAMLResponse to exchange for a Genesys Cloud Access Token:
      1. In Genesys Cloud Admin, select Integrations>OAuth, then click Add Client.
      2. Name the Client and select SAML2 Bearer as the Grant Type.
      3. Enter the Authorized redirect URI, for example:
        Hybrid SAML2Bearer Creation.png
      4. Next, select Authorized Applications and include the scope(s) in the authorization.
        Hybrid SAML2Bearer Authorization.png
      5. Copy the client ID and Secret for later use.
  2. Create your SAML Certificate (public key) and private key. You can perform this task with open source tools or with the tools preferred by your IT department for security purposes. Whichever tools you use, you must produce both private and public keys in the form of a PEM file. For example:
    openssl req -new -x509 -days 3652 -nodes -out cert.pem -keyout key.pem

    Save the cert.pem (public key) and key.pem (private key) for use in the creation of the Transaction object described in the next section.

  3. Create a Genesys Engage Identity Provider (IDP). You can use the Identity Provider API via the Genesys Cloud Developer Tools, SDKs, or Platform APIs.
    Sample Request:
    PUT https://api.{{environment}}/api/v2/identityproviders/pureengage
       "name": "Genesys Engage",
       "autoProvisionUsers": true,
       "certificate": "Content of the cert.pem file without the ---BEGIN CERTIFICATE— and ---END CERTIFICATE--- text blocks",
       "issuerURI": "",
       "ssoTargetURI": "",
       "disabled": false

    issuerURI: the URI set when you created the SAML certificate in Step 2 (above).

    ssoTargetURI: the http redirect URL which should resolve to your Genesys Cloud domain. Example: (domain varies according to your region).


    • Ensure that the IDP is set with "autoProvisionUsers" = "true"
    • Ensure an exact match with the saml/issuer option of the Transaction object described in the Genesys Engage configuration.
    • Ensure that you don't have multiple issuers with the same URI.
  4. By default, Genesys Predictive Engagement permissions are included in the Admin and AI Agent roles (which includes all necessary permissions for using Genesys Predictive Engagement). As auto-provisioned users are created with the employee role, which does not include Genesys Predictive Engagement permissions. You must grant the Altocloud permissions to the employee role. You may grant Genesys Predictive Engagement permissions to additional roles as needed. Copy these role names for the Genesys Engage On Premises: Transaction object for hybrid integrations steps below.
  5. (Optional as needed) Create additional Admin accounts by adding people to your organization and assigning them to the Admin role.

Genesys Engage On Premises: Transaction object for hybrid integrations

A transaction object is needed for Genesys components to authenticate with Genesys Cloud.

  1. Create a transaction object (and alias) of type list named hybrid_integration in the Transaction folder of the Environment tenant.
    • Tenant characteristics:
      • Single tenant deployment: If your Genesys Engage deployment is not multi-tenant, the transaction object should be in the Transaction folder in the Environment or Resources structure.
      • Multi-tenant deployment: If your Genesys Engage deployment is multi-tenant, there must be a separate transaction object under each of the tenant structures. The transaction objects represent the connectivity to the different Genesys Cloud Orgs representing these different tenants. You cannot place a transaction object in the Environment structure and share it across tenants because you need a separate Genesys Cloud Org for each tenant.
        WARNING: If you are running Workspace Desktop Edition, you must ensure that the agents of a Tenant do not have READ access on the 'hybrid_integration' Transaction objects of the other tenants.
  2. Create the following Object options in the general section:
    • organization_sname: The Genesys Cloud organization short name for this tenant.
    • organization_id: The Genesys Cloud organization id for this tenant.
    • default_agent_role_name: The default Genesys Cloud agent role name for an AI Agent. This will always be employee.
    • default_admin_role_name: The default Genesys Cloud admin role name. This is admin.
    • base_auth_url: The base auth URL that can be used for any Genesys Cloud service; for example: base_auth_url should be https://[region_host]/oauth/token (for example: ""). [region_host] is the authentication-based FQDN for the region; the regions are listed on this page.
    • base_service_url: The base URL that can be used for any Genesys Cloud service; for example: base_service_url should be https://[region_host]/api/. [region_host] should be the API-based FQDN for the region; the regions are listed on this page. The rest of the URL is Genesys Cloud service and version specific; for example: ...v2/conversations. The base_service_url and the service specific portion is combined in your component code.
    • organization_domain_suffix: Create this option in the Annex of the "hybrid_integration" transaction object. If the username of the agent in the Genesys Engage system is not defined as an email address, this option is appended to the Genesys Cloud organization short name for this tenant (organization_sname) to generate a username with valid email format. A valid value is a string representing a valid DNS top-domain. The default value is com.
  3. Use the two PEM files that you created in the Genesys Cloud Provisioning section to perform the following steps. This example show you how to do it in an open source tool; check with your IT department to determine the best tool to use to meet your security requirements.
    • Encode cert.pem into a base64 string (cert.pem.b64) using this command:
      openssl base64 -in cert.pem -out cert.pem.b64
    • Encrypt the key.pem using a password that you specify
      openssl rsa -in key.pem -out key.pem.enc -aes256
    • Encode the resulting content into a base64 string (=>’key.pem.enc.b64’) using this command:
      openssl base64 -in key.pem.enc -out key.pem.enc.b64
  4. Create the following Object options in the saml section:
    • issuer: The SAML IDP URI that you created in the Genesys Cloud Provisioning steps above (for example:
    • certificate: The content of the public key of the SAML certificate encoded in base64; for example: cert.pem.b64 created in step 3.
    • pkey: The content of the encrypted private key of the SAML related certificate encoded in base64; for example: key.pem.enc.b64 created in step 3.
    • password: The password to decrypt the private key that you specified in step 3.
    • expire_time: The expiration time (in hours) for the access token. The default is 24 hours. This might be overridden on the server side.
  5. For each Genesys Engage service that uses a Genesys Cloud common service (specified at step#1) you must create a dedicated section in the Transaction object:
    • Create the following Object options in the saml_auth section for the OAuth client for SAML Authentication from the client (such as Workspace Desktop Edition) that you created in step 1b of the Genesys Cloud Provisioning section of type SAML2 Bearer:
      • client_id: The SAML2 Bearer client ID created in step 1b of the Genesys Cloud Provisioning section.
      • password: The SAML2 Bearer client secret created in step 1b of the Genesys Cloud Provisioning section.
    • For the Agent Pacing Service, create the following Object options in the ewt section for the pacing engine to connect to Genesys Cloud:
      • client_id: The Client Credential Grant Client ID that you created in step 1c of the Genesys Cloud Provisioning section.
      • password: The Client Credential Grant Client secret that you created in step 1c of the Genesys Cloud Provisioning section.

Opening Your Network

You must modify the permissions on our network to permit the Genesys Engage Components and UIs to access Genesys Cloud Common APIs over your network and into the Internet. To do this, you must create a set of new firewall rules for the Genesys Cloud Authentication and Common Services URLs.

Retrieved from " (2020-10-31 20:17:04)"