- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-11-2023 07:42 AM
I am setting up a process to pull data for many customers using Webex CC. There is a refresh token that is provided but expires every 60 days. Instead of the customer generating a new code ever 60 days that generates a new refresh and auth token, I'd like to know how to push the expiration date of the current refresh token out OR get a new refresh token with a new expiration date without creating a new Code.
This is the documentation i'm currently using.
https://developer.webex-cx.com/documentation/authentication
Solved! Go to Solution.
- Labels:
-
Webex Contact Center APIs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-11-2023 07:59 AM
Hi @dwynn2 ,
one such method was covered in the sample “Token management Sample” where we go over the process of background refresh without user intervention.
the initial access token, refresh token, needs to be generated through the form based/ user initiated OAuth. You can do this via postman or have an integration page on your app with a button to trigger the flow.
the rest is via a backend scheduler service that generates an access and refresh token pair. Both access and refresh tokens will change eventually near the 59 day mark hence your service will persist this pair via some method. In the example we use a simple database with a single row per orgID for the token(your app could onboard any number of customers)
https://github.com/CiscoDevNet/webex-contact-center-api-samples/tree/main/token-app-sample
Thanks and Regards,
Arunabh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-11-2023 07:59 AM
Hi @dwynn2 ,
one such method was covered in the sample “Token management Sample” where we go over the process of background refresh without user intervention.
the initial access token, refresh token, needs to be generated through the form based/ user initiated OAuth. You can do this via postman or have an integration page on your app with a button to trigger the flow.
the rest is via a backend scheduler service that generates an access and refresh token pair. Both access and refresh tokens will change eventually near the 59 day mark hence your service will persist this pair via some method. In the example we use a simple database with a single row per orgID for the token(your app could onboard any number of customers)
https://github.com/CiscoDevNet/webex-contact-center-api-samples/tree/main/token-app-sample
Thanks and Regards,
Arunabh
