Difference between revisions of "Draft: PEC-Hybrid/Current/Admin/About"

From Genesys Documentation
Jump to: navigation, search
Line 84: Line 84:
 
</source>
 
</source>
 
Save the cert.pem (private key) and key.pem for use in the creation of the Transaction object described in the next section.
 
Save the cert.pem (private key) and key.pem for use in the creation of the Transaction object described in the next section.
</li>
 
</ul>
 
 
</li>
 
</li>
 
<li>Create a PureEngage Identity Provider (IDP). You can use the Identity Provider API via the [https://developer.mypurecloud.com/developer-tools/#/api-explorer PureCloud 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 PureEngage Identity Provider (IDP). You can use the Identity Provider API via the [https://developer.mypurecloud.com/developer-tools/#/api-explorer PureCloud Developer Tools], [https://developer.mypurecloud.com/api/rest/client-libraries/ SDKs], or [https://developer.mypurecloud.com/api/rest/v2/identityprovider/ Platform APIs].<br>

Revision as of 17:48, June 5, 2019

This is a draft page; the published version of this page can be found at PEC-Hybrid/Current/Admin/About.

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

Supported Services

About Provisioning

PureCloud Provisioning Steps

PureEngage On Premises: Transaction object for hybrid integrations

Opening Your Network