Difference between revisions of "Draft: PEC-Hybrid/Current/Admin/About"
From Genesys Documentation
| Line 83: | Line 83: | ||
openssl req -new -x509 -days 3652 -nodes -out cert.pem -keyout key.pem | openssl req -new -x509 -days 3652 -nodes -out cert.pem -keyout key.pem | ||
</source> | </source> | ||
| − | Save the cert.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. |
</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> | ||
| Line 102: | Line 102: | ||
<ul> | <ul> | ||
<li>Ensure that the IDP is set with "autoProvisionUsers" = "true"</li> | <li>Ensure that the IDP is set with "autoProvisionUsers" = "true"</li> | ||
| − | <li>Ensure | + | <li>Ensure an exact match with the saml/issuer option of the Transaction object described in the PureEngage configuration.</li> |
<li>Ensure that you don't have multiple issuers with the same URI.</li> | <li>Ensure that you don't have multiple issuers with the same URI.</li> | ||
</ul> | </ul> | ||
| Line 166: | Line 166: | ||
<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> | <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> | ||
</ul> | </ul> | ||
| − | For each PureEngage service that uses a PureCloud common service (specified at step#1) you must create a dedicated section in the Transaction object: | + | </li> |
| + | <li>For each PureEngage service that uses a PureCloud common service (specified at step#1) you must create a dedicated section in the Transaction object: | ||
<ul> | <ul> | ||
<li>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 PureCloud Provisioning section of type SAML2 Bearer: | <li>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 PureCloud Provisioning section of type SAML2 Bearer: | ||
Revision as of 12:33, June 6, 2019
This is a draft page; the published version of this page can be found at PEC-Hybrid/Current/Admin/About.
Contents
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.