PEC-Hybrid/Current/Admin/About - Revision history

Bgrenon: Redirected page to ATC/ProvisioningMulticloudCX

2022-02-10T18:41:14Z

Redirected page to ATC/ProvisioningMulticloudCX

Show changes

Ed.jamer@genesys.com: Text replacement - "Genesys Cloud" to "Genesys Cloud CX"

2021-11-09T21:28:07Z

Text replacement - "Genesys Cloud" to "Genesys Cloud CX"

Show changes

Ed.jamer@genesys.com: Text replacement - "Gxxx Exxx on-premises" to "Genesys Engage on-premises"

2021-11-09T21:18:13Z

Text replacement - "Gxxx Exxx on-premises" to "Genesys Engage on-premises"

Ed.jamer@genesys.com: Text replacement - "Genesys Engage" to "Genesys Multicloud CX"

2021-11-09T21:11:52Z

Text replacement - "Genesys Engage" to "Genesys Multicloud CX"

Show changes

Ed.jamer@genesys.com: Text replacement - "Genesys Engage [oO]n-[pP]remises" to "Gxxx Exxx on-premises"

2021-11-09T21:07:21Z

Text replacement - "Genesys Engage [oO]n-[pP]remises" to "Gxxx Exxx on-premises"

Matthew.west@genesys.com: Published

2021-04-14T14:19:11Z

Published

Ed.jamer@genesys.com: Text replacement - "Altocloud([. ])" to "Predictive Engagement$1"

2020-11-17T15:02:46Z

Text replacement - "Altocloud([. ])" to "Predictive Engagement$1"

Matthew.west@genesys.com: Published

2020-10-20T18:24:40Z

Published

WikiSysop: Text replacement - "\|Platform=([^\|])GenesysEngage-onpremises([\|])" to "|Platform=$1GenesysEngage-cloud$2"

2020-07-25T02:31:49Z

Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2"

WikiSysop: Text replacement - "PureCloud" to "Genesys Cloud"

2020-07-15T12:05:43Z

Text replacement - "PureCloud" to "Genesys Cloud"

Show changes

@@ Line 3: / Line 3: @@
 |DisplayName=Provisioning Genesys Multicloud CX Hybrid Integrations
 |TocName=Provisioning
-|Context=This article describes the essential provisioning steps to enable a hybrid integration between Gxxx Exxx on-premises deployments and Genesys Cloud services. This enables you to access many of the great Genesys Cloud Services in your On-Premises deployments.
+|Context=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.
 |ComingSoon=No
 |Platform=GenesysEngage-cloud
@@ Line 13: / Line 13: @@
 *{{Link-AnywhereElse|product=ATC|display text=Genesys Predictive Engagement}} (formerly Predictive Engagement)
-**{{Link-AnywhereElse|product=ATC|version=Current|manual=WDEPlugin|topic=About|display text=Genesys Predictive Engagement for Workspace Desktop Edition}} (formerly Predictive Engagement). Refer to {{Link-Standalone|topic=Solution/EngagePredictiveEngagement}} for more information on integrating Genesys Predictive Engagement into Gxxx Exxx on-premises.
+**{{Link-AnywhereElse|product=ATC|version=Current|manual=WDEPlugin|topic=About|display text=Genesys Predictive Engagement for Workspace Desktop Edition}} (formerly Predictive Engagement). Refer to {{Link-Standalone|topic=Solution/EngagePredictiveEngagement}} for more information on integrating Genesys Predictive Engagement into Genesys Engage on-premises.
 **{{Link-AnywhereElse|product=ATC|version=Current|manual=PacingServiceDeployment|topic=About|display text=Agent Pacing Service}}
@@ Line 23: / Line 23: @@
 |structuredtext=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 Multicloud CX Configuration Server. Gxxx Exxx on-premises Services, Components, and UIs will use this information to authenticate with the Genesys Cloud Common Services and UIs.
+To support the different authentication mechanisms in Genesys Cloud Integration, you must create a transaction object in Genesys Multicloud CX 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.

@@ Line 3: / Line 3: @@
 |DisplayName=Provisioning Genesys Engage Hybrid Integrations
 |TocName=Provisioning
-|Context=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.
+|Context=This article describes the essential provisioning steps to enable a hybrid integration between Gxxx Exxx on-premises deployments and Genesys Cloud services. This enables you to access many of the great Genesys Cloud Services in your On-Premises deployments.
 |ComingSoon=No
 |Platform=GenesysEngage-cloud
@@ Line 13: / Line 13: @@
 *{{Link-AnywhereElse|product=ATC|display text=Genesys Predictive Engagement}} (formerly Predictive Engagement)
-**{{Link-AnywhereElse|product=ATC|version=Current|manual=WDEPlugin|topic=About|display text=Genesys Predictive Engagement for Workspace Desktop Edition}} (formerly Predictive Engagement). Refer to {{Link-Standalone|topic=Solution/EngagePredictiveEngagement}} for more information on integrating Genesys Predictive Engagement into Genesys Engage on-premises.
+**{{Link-AnywhereElse|product=ATC|version=Current|manual=WDEPlugin|topic=About|display text=Genesys Predictive Engagement for Workspace Desktop Edition}} (formerly Predictive Engagement). Refer to {{Link-Standalone|topic=Solution/EngagePredictiveEngagement}} for more information on integrating Genesys Predictive Engagement into Gxxx Exxx on-premises.
 **{{Link-AnywhereElse|product=ATC|version=Current|manual=PacingServiceDeployment|topic=About|display text=Agent Pacing Service}}
@@ Line 23: / Line 23: @@
 |structuredtext=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.
+To support the different authentication mechanisms in Genesys Cloud Integration, you must create a transaction object in Genesys Engage Configuration Server. Gxxx Exxx 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.

@@ Line 12: / Line 12: @@
 |structuredtext=The following [https://help.mypurecloud.com Genesys Cloud services] are supported and have supplementary documentation:
-*{{Link-AnywhereElse|product=ATC|display text=Genesys Predictive Engagement}} (formerly Altocloud)
+*{{Link-AnywhereElse|product=ATC|display text=Genesys Predictive Engagement}} (formerly Predictive Engagement)
-**{{Link-AnywhereElse|product=ATC|version=Current|manual=WDEPlugin|topic=About|display text=Genesys Predictive Engagement for Workspace Desktop Edition}} (formerly Altocloud). Refer to {{Link-Standalone|topic=Solution/EngagePredictiveEngagement}} for more information on integrating Genesys Predictive Engagement into Genesys Engage on-premises.
+**{{Link-AnywhereElse|product=ATC|version=Current|manual=WDEPlugin|topic=About|display text=Genesys Predictive Engagement for Workspace Desktop Edition}} (formerly Predictive Engagement). Refer to {{Link-Standalone|topic=Solution/EngagePredictiveEngagement}} for more information on integrating Genesys Predictive Engagement into Genesys Engage on-premises.
 **{{Link-AnywhereElse|product=ATC|version=Current|manual=PacingServiceDeployment|topic=About|display text=Agent Pacing Service}}
@@ Line 36: / Line 36: @@
 *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 https://login.mypurecloud.com (or a [https://developer.mypurecloud.com/api/rest/index.html 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.
+As an administrator, you may access your Genesys Cloud organization by logging in at https://login.mypurecloud.com (or a [https://developer.genesys.cloud/api/rest/index.html 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 [https://developer.mypurecloud.com/api/rest/v2/ Genesys Cloud API].
+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 [https://developer.genesys.cloud/api/rest/v2/ Genesys Cloud API].
-With the credentials provided in the Welcome email, you can log in to the '''Genesys Cloud Admin''' UI for [https://developer.mypurecloud.com/api/rest/index.html your region] to perform the provisioning steps described in the next section.
+With the credentials provided in the Welcome email, you can log in to the '''Genesys Cloud Admin''' UI for [https://developer.genesys.cloud/api/rest/index.html your region] to perform the provisioning steps described in the next section.
 #In the '''Genesys Cloud Admin''' UI, select '''Account Settings'''.
@@ Line 56: / Line 56: @@
 <li><p>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.)</p>
 <p>Genesys recommends that you consult architecture before performing this step.</p>
-<p>Login to your [https://developer.mypurecloud.com/api/rest/index.html Genesys Cloud Region], then follow these steps:</p>
+<p>Login to your [https://developer.genesys.cloud/api/rest/index.html Genesys Cloud Region], then follow these steps:</p>
 <ol type="a">
 <li>Create a Client Credential OAuth Client that is to based on the specific services you are using, such as the [https://all.docs.genesys.com/ATC/Current/PacingServiceDeployment/ProvisioningArticle 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.<br>
@@ Line 67: / Line 67: @@
 [[File:Hybrid_Client_Credential_OAuth_Grant.png|500px]]
 </li>
-<li>Or using the API, reference [https://developer.mypurecloud.com/api/rest/v2/oauth/ these endpoints].</li>
+<li>Or using the API, reference [https://developer.genesys.cloud/api/rest/v2/oauth/ these endpoints].</li>
 <li>Copy the client ID and Secret for later use.</li>
 </ul>
@@ Line 93: / Line 93: @@
 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.
 </li>
-<li>Create a Genesys Engage Identity Provider (IDP). You can use the Identity Provider API via the [https://developer.mypurecloud.com/developer-tools/#/api-explorer Genesys Cloud Developer Tools], [https://developer.mypurecloud.com/api/rest/client-libraries/ SDKs], or [https://developer.mypurecloud.com/api/rest/v2/identityprovider/ Platform APIs].<br>
+<li>Create a Genesys Engage Identity Provider (IDP). You can use the Identity Provider API via the [https://developer.genesys.cloud/developer-tools/#/api-explorer Genesys Cloud Developer Tools], [https://developer.genesys.cloud/api/rest/client-libraries/ SDKs], or [https://developer.genesys.cloud/api/rest/v2/identityprovider/ Platform APIs].<br>
 Sample Request:<br>
 <source lang="text">
@@ Line 144: / Line 144: @@
 <li>'''default_agent_role_name''': The default Genesys Cloud agent role name for an '''AI Agent'''. This will always be '''employee'''. </li>
 <li>'''default_admin_role_name''': The default Genesys Cloud admin role name. This is '''admin'''.</li>
-<li>'''base_auth_url''': The base auth URL that can be used for any Genesys Cloud service; for example: '''base_auth_url''' should be <nowiki>https://[region_host]/oauth/token</nowiki> (for example: <nowiki>"https://login.mypurecloud.com/oauth/token"</nowiki>). <nowiki>[region_host]</nowiki> is the authentication-based FQDN for the region; the regions are listed on [https://developer.mypurecloud.com/api/rest/ this page].</li>
+<li>'''base_auth_url''': The base auth URL that can be used for any Genesys Cloud service; for example: '''base_auth_url''' should be <nowiki>https://[region_host]/oauth/token</nowiki> (for example: <nowiki>"https://login.mypurecloud.com/oauth/token"</nowiki>). <nowiki>[region_host]</nowiki> is the authentication-based FQDN for the region; the regions are listed on [https://developer.genesys.cloud/api/rest/ this page].</li>
-<li>'''base_service_url''': The base URL that can be used for any Genesys Cloud service; for example: '''base_service_url''' should be <nowiki>https://[region_host]/api/</nowiki>. <nowiki>[region_host]</nowiki> should be the API-based FQDN for the region; the regions are listed on [https://developer.mypurecloud.com/api/rest/ 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.</li>
+<li>'''base_service_url''': The base URL that can be used for any Genesys Cloud service; for example: '''base_service_url''' should be <nowiki>https://[region_host]/api/</nowiki>. <nowiki>[region_host]</nowiki> should be the API-based FQDN for the region; the regions are listed on [https://developer.genesys.cloud/api/rest/ 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.</li>
 <li>'''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'''.</li>
 </ul>

@@ Line 70: / Line 70: @@
 <li>Copy the client ID and Secret for later use.</li>
 </ul>
-For more information about Permissions for Genesys Predictive Engagement, see the [https://help.mypurecloud.com/articles/altocloud-permissions-overview/ Altocloud permissions overview].
+For more information about Permissions for Genesys Predictive Engagement, see the [https://help.mypurecloud.com/articles/altocloud-permissions-overview/ Predictive Engagement permissions overview].
 </li>
 <li>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:
@@ Line 116: / Line 116: @@
 </ul>
 </li>
-<li>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 [https://help.mypurecloud.com/articles/altocloud-permissions-overview/ 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.</li>
+<li>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 [https://help.mypurecloud.com/articles/altocloud-permissions-overview/ Predictive Engagement 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.</li>
 <li>(Optional as needed) Create additional '''Admin''' accounts by [https://help.mypurecloud.com/articles/add-people-organization/ adding people to your organization] and [https://help.mypurecloud.com/articles/assign-roles-divisions-licenses-and-add-ons/ assigning them] to the '''Admin''' role.</li>
 </ol>

@@ Line 2: / Line 2: @@
 |Standalone=Yes
 |DisplayName=Provisioning Genesys Engage Hybrid Integrations
 |TocName=Provisioning
 |ComingSoon=No
-|Context=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.
+|Platform=GenesysEngage-cloud
 |Section={{Section
 |sectionHeading=Supported Services
-|Standalone=No
+|anchor=SupportedServices
 |alignment=Vertical
 |structuredtext=The following [https://help.mypurecloud.com Genesys Cloud services] are supported and have supplementary documentation:
-* {{Link-AnywhereElse|product=ATC|display text=Genesys Altocloud}}
-** {{Link-AnywhereElse|product=ATC|version=Current|manual=WDEPlugin|topic=About|display text=Altocloud for Workspace Desktop Edition}}
+*{{Link-AnywhereElse|product=ATC|display text=Genesys Predictive Engagement}} (formerly Altocloud)
-** {{Link-AnywhereElse|product=ATC|version=Current|manual=PacingServiceDeployment|topic=About|display text=Agent Pacing Service}}
+**{{Link-AnywhereElse|product=ATC|version=Current|manual=WDEPlugin|topic=About|display text=Genesys Predictive Engagement for Workspace Desktop Edition}} (formerly Altocloud). Refer to {{Link-Standalone|topic=Solution/EngagePredictiveEngagement}} for more information on integrating Genesys Predictive Engagement into Genesys Engage on-premises.
 |Status=No
 }}{{Section
 |sectionHeading=About Provisioning
-|Standalone=No
+|anchor=About
 |alignment=Vertical
 |structuredtext=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.
@@ Line 32: / Line 30: @@
 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.
+*The base functionality required for 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.
+*An '''Admin console''' that you may use to configure your Common Cloud integration.
-* A default '''AI Agent''' role (if required by your integration) that provides agent access to AI services, such as Altocloud.
+*A user with the '''Genesys Cloud Admin''' role, which includes default admin permissions as well as Single Sign-On and any integration-specific permissions.
 As an administrator, you may access your Genesys Cloud organization by logging in at https://login.mypurecloud.com (or a [https://developer.mypurecloud.com/api/rest/index.html 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.
@@ Line 42: / Line 41: @@
 With the credentials provided in the Welcome email, you can log in to the '''Genesys Cloud Admin''' UI for [https://developer.mypurecloud.com/api/rest/index.html your region] to perform the provisioning steps described in the next section.
 # In the '''Genesys Cloud Admin''' UI, select '''Account Settings'''.
-# Open '''Organization Settings'''.
+#In the '''Genesys Cloud Admin''' UI, select '''Account Settings'''.
-# In the '''Organization Details''' tab, open '''Advanced'''.
+#Open '''Organization Settings'''.
-# Copy the Company Name, Short Name, and Organization ID &mdash; you will need these values to complete your account configuration in the '''Genesys Engage On Premises: Transaction object for hybrid integrations''' section. For example:<br>[[File:Hybrid_Organization_Name_And_ID.png|500px]]
+#In the '''Organization Details''' tab, open '''Advanced'''.
-The following diagram provides an overview of how Genesys Engage utilizes Genesys Cloud services such as Altocloud:<br>[[File:Hybrid_Genesys Engage_Premise_Integration_Phase_1.png|500px]]
+#Copy the Company Name, Short Name, and Organization ID &mdash; you will need these values to complete your account configuration in the '''Genesys Engage On Premises: Transaction object for hybrid integrations''' section. For example:<br>[[File:Hybrid_Organization_Name_And_ID.png|500px]]
 |Status=No
-}}
+}}{{Section
 |sectionHeading=Genesys Cloud Provisioning Steps
 |alignment=Vertical
 |structuredtext=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.
@@ Line 72: / Line 70: @@
 <li>Copy the client ID and Secret for later use.</li>
 </ul>
-For more information about Permissions for Altocloud, see the [https://help.mypurecloud.com/articles/altocloud-permissions-overview/ Altocloud permissions overview].
+For more information about Permissions for Genesys Predictive Engagement, see the [https://help.mypurecloud.com/articles/altocloud-permissions-overview/ Altocloud permissions overview].
 </li>
 <li>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:
@@ Line 118: / Line 116: @@
 </ul>
 </li>
-<li>By default, Altocloud permissions are included in the '''Admin''' and '''AI Agent''' roles (which includes all necessary permissions for using Altocloud). As auto-provisioned users are created with the '''employee''' role, which does not include Altocloud permissions. You must grant the [https://help.mypurecloud.com/articles/altocloud-permissions-overview/ Altocloud permissions] to the employee role. You may grant Altocloud permissions to additional roles as needed. Copy these role names for the '''Genesys Engage On Premises: Transaction object for hybrid integrations''' steps below.</li>
+<li>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 [https://help.mypurecloud.com/articles/altocloud-permissions-overview/ 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.</li>
 <li>(Optional as needed) Create additional '''Admin''' accounts by [https://help.mypurecloud.com/articles/add-people-organization/ adding people to your organization] and [https://help.mypurecloud.com/articles/assign-roles-divisions-licenses-and-add-ons/ assigning them] to the '''Admin''' role.</li>
 </ol>
@@ Line 124: / Line 122: @@
 }}{{Section
 |sectionHeading=Genesys Engage On Premises: Transaction object for hybrid integrations
-|Standalone=No
+|anchor=TransactionObjHybrid
 |alignment=Vertical
 |structuredtext=A transaction object is needed for Genesys components to authenticate with Genesys Cloud.
 <ol>
@@ Line 175: / Line 171: @@
 <ul>
 <li>'''issuer''': The SAML IDP URI that you created in the Genesys Cloud Provisioning steps above (for example: <nowiki>https://www.genesys.com/pureengage</nowiki>).</li>
-<li>'''certificate''': The public key of the SAML related certificate encoded in base64; for example: cert.pem.b64 created in step 3.</li>
+<li>'''certificate''': The content of the public key of the SAML certificate encoded in base64; for example: cert.pem.b64 created in step 3.</li>
-<li>'''pkey''': The encrypted private key of the SAML related certificate encoded in base64; for example: key.pem.enc.b64 created in step 3.</li>
+<li>'''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.</li>
 <li>'''password''': The password to decrypt the private key that you specified in step 3.</li>
 <li>'''expire_time''': The expiration time (in hours) for the access token. The default is 24 hours. This might be overridden on the server side.</li>
@@ Line 201: / Line 197: @@
 }}{{Section
 |sectionHeading=Opening Your Network
 |alignment=Vertical
 |structuredtext=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.

PEC-Hybrid/Current/Admin/About - Revision history

Bgrenon: Redirected page to ATC/ProvisioningMulticloudCX

Ed.jamer@genesys.com: Text replacement - "Genesys Cloud" to "Genesys Cloud CX"

Ed.jamer@genesys.com: Text replacement - "Gxxx Exxx on-premises" to "Genesys Engage on-premises"

Ed.jamer@genesys.com: Text replacement - "Genesys Engage" to "Genesys Multicloud CX"

Ed.jamer@genesys.com: Text replacement - "Genesys Engage [oO]n-[pP]remises" to "Gxxx Exxx on-premises"

Matthew.west@genesys.com: Published

Ed.jamer@genesys.com: Text replacement - "Altocloud([. ])" to "Predictive Engagement$1"

Matthew.west@genesys.com: Published

WikiSysop: Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2"

WikiSysop: Text replacement - "PureCloud" to "Genesys Cloud"

WikiSysop: Text replacement - "\|Platform=([^\|])GenesysEngage-onpremises([\|])" to "|Platform=$1GenesysEngage-cloud$2"