Difference between revisions of "Draft: PEC-Hybrid/Current/Admin/About"
From Genesys Documentation
| Line 161: | Line 161: | ||
<ul> | <ul> | ||
<li>'''issuer''': The SAML IDP URI that you created in the PureCloud Provisioning steps above (for example: <nowiki>https://www.genesys.com/pureengage</nowiki>).</li> | <li>'''issuer''': The SAML IDP URI that you created in the PureCloud 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 | + | <li>'''certificate''': The public key of the SAML related 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 | + | <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>'''password''': The password to decrypt the private key that you specified in step | + | <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> | <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> | ||
| Line 170: | Line 170: | ||
<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 1a 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 1a of type SAML2 Bearer: | ||
<ul> | <ul> | ||
| − | <li>'''client_id''': The SAML2 Bearer client ID created in step 1a</li> | + | <li>'''client_id''': The SAML2 Bearer client ID created in step 1a of the PureCloud Provisioning section.</li> |
| − | <li>'''password''': The SAML2 Bearer client secret created in step 1a</li> | + | <li>'''password''': The SAML2 Bearer client secret created in step 1a of the PureCloud Provisioning section.</li> |
</ul> | </ul> | ||
</li> | </li> | ||
<li>For the Agent Pacing Service, create the following Object options in the '''ewt''' section for the pacing engine to connect to PureCloud: | <li>For the Agent Pacing Service, create the following Object options in the '''ewt''' section for the pacing engine to connect to PureCloud: | ||
<ul> | <ul> | ||
| − | <li>'''client_id''': The Client Credential Grant Client ID that you created in step 1b.</li> | + | <li>'''client_id''': The Client Credential Grant Client ID that you created in step 1b of the PureCloud Provisioning section.</li> |
| − | <li>'''password''': The Client Credential Grant Client secret that you created in step 1b.</li> | + | <li>'''password''': The Client Credential Grant Client secret that you created in step 1b of the PureCloud Provisioning section.</li> |
</ul> | </ul> | ||
</li> | </li> | ||
Revision as of 17:52, June 5, 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.