Webex Contact Center Revoke Token API

[W S H FERNANDO]

Hi Cisco Team

We are using Webex CC APIs and we use generate and refresh token APIs. We are hitting the 650 limit of number of API tokens. 

Since we cannot store the Token with a timestamp in a GV via FLow, we need to release the token after each call/session. 

Please guide us on how we can achieve this. is there any API token Revolve API?  any documentation? 

Thanks

[W S H FERNANDO]

@Arunabh Bhattacharjee 

The information that you provided is very helpful. Thanks a lot, Arunabh. 

[Arunabh Bhattacharjee · Accepted solution]

Here is the schematic on how this middleware can be hosted and used with Flow designer today - again, this is more of a workaround because Flow Designer today does not support the OAuth2 Node with "authorization_code" grant type.

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

[Arunabh Bhattacharjee]

Hi @W S H FERNANDO 

The logout URL for Common Identity is 

GET https://idbroker.webex.com/idb/oauth2/v1/logout

That will revoke the Token - you can test this in the lab, it will revoke the token and release the access token.

Also, what is important is that for within Flow designer - you need to use a Token Management service that auto-refreshes the tokens every 10 hours - as opposed to using 1 token per call flow.

So in the call flow - you will first call the middleware - and then get the most recent token and access the API,

the example is posted here along with the vidcast in the ReadMe.md 

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

When pushing this to production, you may want to use a different backend and other authentication mechanisms. 

A permanent solution to this above "workaround" is to allow direct access of our APIs from within Flow Designer. 

This is on the roadmap - there is no concrete date available yet but it is under discussion.

Thanks & Regards,

Arunabh.