Difference between revisions of "Draft: PEC-Hybrid/Current/Admin/About"
From Genesys Documentation
| Line 126: | Line 126: | ||
<li>Tenant characteristics: | <li>Tenant characteristics: | ||
<ul> | <ul> | ||
| − | <li>If your PureEngage deployment is ''not'' multi-tenant, the transaction object should be put under the '''Environment''' structure.</li> | + | <li>'''Single tenant deployment''': If your PureEngage deployment is ''not'' multi-tenant, the transaction object should be put under the '''Environment''' structure.</li> |
| − | <li>If your PureEngage deployment is multi-tenant, there must be a separate transaction object under ''each'' of the tenant structures. The transaction objects represent the connectivity to the different PureCloud Orgs representing these different tenants. You ''cannot'' place a transaction object in the Environment structure and share it across tenants because you need a separate PureCloud Org for each tenant.</li> | + | <li>'''Multi-tenant deployment''': If your PureEngage deployment is multi-tenant, there must be a separate transaction object under ''each'' of the tenant structures. The transaction objects represent the connectivity to the different PureCloud Orgs representing these different tenants. You ''cannot'' place a transaction object in the Environment structure and share it across tenants because you need a separate PureCloud Org for each tenant.</li> |
</ul> | </ul> | ||
</li> | </li> | ||
| Line 146: | Line 146: | ||
<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 (a base64 saml.pem PEM encoded key).</li> | <li>'''certificate''': The public key of the SAML related certificate (a base64 saml.pem PEM encoded key).</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>'''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). You must encrypt the private key with a password that you create before you store the key in Config Server.</li> |
| − | <li>'''password''': The password to decrypt the private key.</li> | + | <li>'''password''': The password to decrypt the private key. You must store the password in the '''password''' option. You can use OpenSSL to perform the encryption with your password</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> | <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: | The resulting material can be set in the saml section of the transaction object: | ||
Revision as of 15:20, 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.