Difference between revisions of "Draft: PEC-Hybrid/Current/Admin/About"
From Genesys Documentation
| Line 103: | Line 103: | ||
<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> | ||
| + | </li> | ||
| + | <li>Create SAML Response Assertion to automatically provision users with the desired role in PureCloud. The following is sample code. Do not copy/paste this code. You must populate the code with the values particular to your organization:<br> | ||
| + | <source lang="xml"> | ||
| + | xxx | ||
| + | </source> | ||
</li> | </li> | ||
<li>By default, Altocloud permissions are included in the Admin and AI Agent roles. You may grant [https://help.mypurecloud.com/articles/altocloud-permissions-overview/ Altocloud permissions] to additional roles as needed. | <li>By default, Altocloud permissions are included in the Admin and AI Agent roles. You may grant [https://help.mypurecloud.com/articles/altocloud-permissions-overview/ Altocloud permissions] to additional roles as needed. | ||
</li> | </li> | ||
<li>(Optional as needed) Create additional Admin accounts by [https://help.mypurecloud.com/articles/add-people-organization/ adding people to your organization] and [https://help.mypurecloud.com/articles/assign-roles-divisions-licenses-and-add-ons/ assigning them] to the Admin role.</li> | <li>(Optional as needed) Create additional Admin accounts by [https://help.mypurecloud.com/articles/add-people-organization/ adding people to your organization] and [https://help.mypurecloud.com/articles/assign-roles-divisions-licenses-and-add-ons/ assigning them] to the Admin role.</li> | ||
| − | |||
</ol> | </ol> | ||
|Status=No | |Status=No | ||
| Line 120: | Line 124: | ||
<ul> | <ul> | ||
<!--<li>Usage characteristics: the transaction object should be acquired at start-up and used until the component gets an error from a given API call. If an error occurs, your component should retrieve the hybrid_integration object from config server and try again. If the component still has problems, your component should end the associated processing with an error.</li>--> | <!--<li>Usage characteristics: the transaction object should be acquired at start-up and used until the component gets an error from a given API call. If an error occurs, your component should retrieve the hybrid_integration object from config server and try again. If the component still has problems, your component should end the associated processing with an error.</li>--> | ||
| − | <li>Tenant characteristics: the transaction object should be | + | <li>Tenant characteristics: |
| + | <ul> | ||
| + | <li>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> | ||
| + | </ul> | ||
| + | </li> | ||
</ul> | </ul> | ||
</li> | </li> | ||
Revision as of 15:15, 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.