cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
629
Views
1
Helpful
4
Replies

WxCC: Authenticating with only the Client ID and Client Secret

BlakeR
Level 1
Level 1

Hello,

I'm researching how to authenticate into Webex Contact Center to use the API with only an Integration Client ID and Client Secret.

I'm currently using Postman (webex-contact-center-api-samples/postman-sample at main · CiscoDevNet/webex-contact-center-api-samples · GitHub) to test authentication. When I follow the documentation, https://developer.webex-cx.com/documentation/authentication, I'm still getting prompted to login even after an Admin User approved the Scopes listed in the Integration by following the OAuth URL.

If there is other documentation regarding this, please share the link with me.

1 Accepted Solution

Accepted Solutions

Arunabh Bhattacharjee
Cisco Employee
Cisco Employee

Hi Blake, 

The initial accessToken and refreshToken is required to "continue to background refresh" using the refresh token flow.

The example and vidcast (Readme has embedded vidcast) covers the use case where one needs continues background access to the APIs. For this, one needs to continually refresh the tokens in the background. However it is important to note that the first / initial login is a pre-requisite - so you can seed your app with Postman OR build a UI button on your app to "Onboard" the app onto webexCC. Post that, you can continue to refresh tokens in the background.

https://github.com/CiscoDevNet/webex-contact-center-api-samples/tree/main/token-management-samples/token-app-sample

 

Here is a serverless example 

https://github.com/CiscoDevNet/webex-contact-center-api-samples/tree/main/token-management-samples/token-service-sample 

Thanks & Regards,

Arunabh.

View solution in original post

4 Replies 4

asmvar@1234
Spotlight
Spotlight

Hi there, 

I followed the same link and created dedicate Environment in Postman for WxCC with variables. It works for me.
Sharing screenshot. 

asmvar1234_0-1688649492204.png

 


 

aubreyengland
Level 1
Level 1

So you are authenticating with an account that is different than the following Admin User , correct?


@BlakeR wrote:

... Admin User approved the Scopes listed in the Integration by following the OAuth URL.


 

Arunabh Bhattacharjee
Cisco Employee
Cisco Employee

Hi Blake, 

The initial accessToken and refreshToken is required to "continue to background refresh" using the refresh token flow.

The example and vidcast (Readme has embedded vidcast) covers the use case where one needs continues background access to the APIs. For this, one needs to continually refresh the tokens in the background. However it is important to note that the first / initial login is a pre-requisite - so you can seed your app with Postman OR build a UI button on your app to "Onboard" the app onto webexCC. Post that, you can continue to refresh tokens in the background.

https://github.com/CiscoDevNet/webex-contact-center-api-samples/tree/main/token-management-samples/token-app-sample

 

Here is a serverless example 

https://github.com/CiscoDevNet/webex-contact-center-api-samples/tree/main/token-management-samples/token-service-sample 

Thanks & Regards,

Arunabh.

Thank you for the detailed explanation.

I know that Webex Calling has introduced 'Service Apps' for background service implementations. Do you know if 'Service Apps' will become available for Webex Contact Center as well?