Difference between revisions of "Draft: PEC-Hybrid/Current/Admin/About"
From Genesys Documentation
| Line 22: | Line 22: | ||
|anchor=About | |anchor=About | ||
|freetext=Before proceeding with the information in this article you should consult with the Genesys Professional Services team that you are working with to obtain the information needed to complete the provisioning. | |freetext=Before proceeding with the information in this article you should consult with the Genesys Professional Services team that you are working with to obtain the information needed to complete the provisioning. | ||
| − | |||
To support the different authentication mechanisms in PureCloud Integration, you must create a transaction object in Genesys Configuration Server under the environment and associated script folder with the following data. PureEngage On-Premises Services, Components, and UIs will use this information to authenticate with the PureCloud Common Services and UIs. | To support the different authentication mechanisms in PureCloud Integration, you must create a transaction object in Genesys Configuration Server under the environment and associated script folder with the following data. PureEngage On-Premises Services, Components, and UIs will use this information to authenticate with the PureCloud Common Services and UIs. | ||
| − | |||
Use Genesys Administrator Extension to manually create all of the PureCloud Common Service–related configuration information in Configuration Server at the Tenant level. | Use Genesys Administrator Extension to manually create all of the PureCloud Common Service–related configuration information in Configuration Server at the Tenant level. | ||
| − | |||
After you purchase a common cloud service, you will receive a welcome email to activate your admin accounts with PureCloud. With those credentials you can log in to the PureCloud Admin UI to perform the provisioning steps described below. | After you purchase a common cloud service, you will receive a welcome email to activate your admin accounts with PureCloud. With those credentials you can log in to the PureCloud Admin UI to perform the provisioning steps described below. | ||
| Line 35: | Line 32: | ||
|sectionHeading=PureCloud Provisioning Steps | |sectionHeading=PureCloud Provisioning Steps | ||
|Type=Unstructured | |Type=Unstructured | ||
| − | |freetext=# As necessary, create OAuth Client Credentials grants | + | |freetext=Perform the following steps using the PureCloud Admin UI or the PureCloud API. |
| − | # | + | # As necessary, for each on-premises service, create OAuth Client Credentials grants: |
| − | # Create | + | #* Using the UI, follow [https://help.mypurecloud.com/articles/create-an-oauth-client/ these steps], |
| − | + | #* Or using the API, follow [https://developer.mypurecloud.com/api/rest/v2/oauth/ these steps]. | |
| − | # | + | #: For more information about the different kinds of Client Grants, see the [https://developer.mypurecloud.com/api/rest/authorization/ Authorization] reference. |
| − | # Create additional Admin accounts | + | #: For more information about Permissions for Altocloud, see the [https://help.mypurecloud.com/articles/altocloud-permissions-overview/ Altocloud permissions overview]. |
| + | # Create an Identity Provider (IDP). This step can be done only by the [https://developer.mypurecloud.com/api/rest/client-libraries/java/IdentityProviderApi.html IdentityProviderApi]. | ||
| + | #: Add the following code:<br> | ||
| + | <source lang="text"> | ||
| + | PUT https://api.{{environment}}/api/v2/identityproviders/pureengage | ||
| + | |||
| + | { | ||
| + | "name": "PureEngage", | ||
| + | "autoProvisionUsers": true, | ||
| + | "certificate": "-----BEGIN CERTIFICATE----- ...== -----END CERTIFICATE-----", | ||
| + | "issuerURI": "http://www.genesys.com/pureengage", | ||
| + | "ssoTargetURI": "http://example.com/target", | ||
| + | "disabled": false | ||
| + | } | ||
| + | </source> | ||
| + | #: Authorization: | ||
| + | #:* Type: OAuth 2.0 | ||
| + | #:* Access Token: request new token | ||
| + | #:* Add authorization data to: Request Headers | ||
| + | #: '''Troubleshooting''': | ||
| + | ## Ensure that the IDP is set with "autoProvisionUsers" = "true" | ||
| + | ## Ensure that the issuer uri in your SAML assertion is the same as the issuer uri for the IDP. | ||
| + | ## Ensure that you don't have multiple issuers with the same uri. | ||
| + | # If you need to grant more Administrator or Supervisor roles, configure Altocloud [https://help.mypurecloud.com/articles/altocloud-permissions-overview/ permissions] as necessary. | ||
| + | # (Optional as needed) Create additional Admin accounts by [https://help.mypurecloud.com/articles/add-people-organization/ adding people to your organization]. | ||
| + | |||
How to get help: | How to get help: | ||
* PureEngage: Bill? | * PureEngage: Bill? | ||
Revision as of 19:23, May 23, 2019
This is a draft page; the published version of this page can be found at PEC-Hybrid/Current/Admin/About.
Contents
Manually provision PureCloud (by creating an Organization) and PureEngage Premise (using Genesys Administrator Extension).