Difference between revisions of "Draft: PEC-Hybrid/Current/Admin/About"
From Genesys Documentation
| Line 66: | Line 66: | ||
</source> | </source> | ||
</li> | </li> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
</ul> | </ul> | ||
</li> | </li> | ||
| Line 148: | Line 142: | ||
<li>'''pkey''': The encrypted SAML related certificate private key (a saml.pkcs8 private key encrypted in aes256 with a password (see password option below) and encoded in base64).</li> | <li>'''pkey''': The encrypted SAML related certificate private key (a saml.pkcs8 private key encrypted in aes256 with a password (see password option below) and encoded in base64).</li> | ||
<li>'''password''': The password to decrypt the private key.</li> | <li>'''password''': The password to decrypt the private key.</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.<br> |
| + | The resulting material can be set in the saml section of the transaction object: | ||
| + | <ul> | ||
| + | <li>certificate=<saml.pem.b64></li> | ||
| + | <li>pkey=<saml.pkcs.enc.b64></li> | ||
| + | <li>password=<saml.pkcs.enc.password></li> | ||
| + | </ul> | ||
| + | </li> | ||
<li>To allow for better control and monitoring of the components using PureCloud Services, for each PureEngage Service that uses a common service you must create multiple sections, one for each OAuth client, in Configuration Server to allow for better control and monitoring of the components using the PureCloud 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.<br /> | <li>To allow for better control and monitoring of the components using PureCloud Services, for each PureEngage Service that uses a common service you must create multiple sections, one for each OAuth client, in Configuration Server to allow for better control and monitoring of the components using the PureCloud 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.<br /> | ||
Genesys recommends that you consult architecture before performing this step. | Genesys recommends that you consult architecture before performing this step. | ||
Revision as of 14:34, May 30, 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 PureEngage On-Prem deployments and Genesys PureCloud services.