Cisco Webex Calling Native Call Control - Imagicle Token Authorizer
Requirements
- Imagicle UC Cloud Suite rel. 2021.Summer.2 and above, with activated subscription licenses
- Imagicle Attendant Console client ver. 2021.Summer.2 or above
- A Full Admin user belonging to Webex Calling customer organization
- Webex Calling Presence already enabled, as described here.
OAuth2 tokens for UC Suite integration with Webex Calling Call Control
Customer must authorize Imagicle Webex Calling Integration application called Attendant Console Call Control Connector to access own Webex organization data. Actually, customer should grant the following permissions to the Imagicle Webex Calling Integration application:
- spark-admin:people_read
- spark-admin:organizations_read
- spark-admin:xsi
These are the minimum permissions required to retrieve basic user information, read organizations information and to invoke the XSI API to perform the call control actions. Without granting such permission, Imagicle can't provide the feature.
Remarks
The authorization process involves a Full Admin user from the customer which, through own Webex account, authorizes Imagicle Integration. The above mentioned authorization may automatically expire as soon as the authorizing user changes own password. Once the authorization is removed, UC Cloud Suite won't be able to retrieve events related to that authorization. To recover the feature, a new authorization process must be executed.
This limitation does not apply if Webex SSO is enabled.
If SSO in not enable, a user password by default expires after five years, as per the documentation (and an admin user can be created without requiring additional licenses).
This limitation is related to the authentication flow implemented by Webex, namely OAuth2 Authorization Code flow, that implies impersonating a user while accessing the Webex APIs. There is no ETA about the removal of this limitation by Cisco side.
Procedure
Please contact Imagicle tech Support to enable this feature, once above requirements and remarks have been acknowledged.
|
||
This article was: |
Prev | Next | |
Product Configuration | Quick Guides |