Hi everyone,
We have a security issue with the web messaging. We ve reduced the thread timeline to something really small and on the agent side it s working fine, it s considered a new conversation after expiration of the thread.
The issue we have is that the threading timeline does not clean the cookie on the customer side. When considering a customer interacting from a public device, this is a high security issue as the history of the conversation remains for 72hours no matter what the threading timeline is. I feel that the expiry of the web messaging cookies should be tide to the threading timeline, or have the ability to set the cookies in session storage instead of local storage.
This problem may force us to rollback to the webChatv2.
Anyone found a workaround?
Thanks a lot
Hi Jacques,
That is current behavior with our native Messenger, as it is focusing on async conversations that can last over time. The threading timeline is completely decoupled from Messenger, see our FAQ here.
We have upcoming features to address the "public/shared" computer use-case:
https://genesyscloud.ideas.aha.io/ideas/DXWMM-I-10
https://genesyscloud.ideas.aha.io/ideas/DXWMM-I-26
https://genesyscloud.ideas.aha.io/ideas/DIG-I-118
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.