In the Finesse framework, the Single Sign-On (SSO) access token is typically managed and refreshed by the Finesse desktop application itself. The responsibility of refreshing the access token lies with the desktop application, and it may use mechanisms such as OAuth 2.0 to obtain a new access token when needed.
When it comes to Finesse gadgets that are also using SSO, each gadget has its own separate context and lifecycle. Therefore, the gadgets would typically need to implement their own mechanism to handle the refreshing of the access token. This means that each SSO gadget would need to make its own API call to fetch a new access token using the Finesse API, as you mentioned with the Fetch Access Token API endpoint.
In this scenario, the gadgets would need to handle the management of the access token themselves and monitor its expiration. If the access token is refreshed, the gadgets can update their own access token accordingly. There is no built-in mechanism in Finesse or the OpenAjax Hub to automatically notify the gadgets when the access token is updated.
It's worth noting that the specific implementation details may depend on the version of Finesse and the gadget framework being used. It's recommended to refer to the Finesse documentation or reach out to the Cisco support team for further guidance on implementing SSO with Finesse gadgets.
mymilestonecard
