Today we have to set JWT token to not expire over a series of hours to prevent more frequent expiry from causing “not authenticated” chat session. And, eventually, and although less frequently they could still be “not authenticated” as there is no method from FW to renew.
This is a request to have a JavaScript async callback method that is expiry-aware and would automatically callback to renew token if user is still actively engaged.
Alternatively, and perhaps even better, would be to provide an in-chat prompt to “For security reasons, please click ‘Stay Connected’ below to refresh your authentication as it is about to expire.” And then, if expired offer an in-chat prompt of “For security reasons, this chat session has expired. To continue chatting, click “Reload Chat Widget” and we’ll reload your entire web page for a new secure chat session.”
