How to setup web widget cookie per subdomain

Hey Christopher, 

This already helped a lot, thank you for that information. So I assume the login-function sent to the Web-Widget would have to be called upon every single page load with the previously(or a newly?) generated JWT-Token of the user, ist that correct?

zE('messenger', 'loginUser', function (callback) {
callback('new-jwt-for-user');
});

Unfortunately the documentation seems to go into a lot of detail in how to create the JWT token, but seems unclear in how the token is supposed to be passed to the Web Widget.

Another question I have is: Is it in anyway possible sharing conversation history for not-authenticated users over main domain - subdomain for the Web Widget? Or are there any plans to set the data to be stored into cookies instead of local storage? 
Right now the only way I can think of would be to share local storage of the main domain with the sub domain, via an Iframe workaround, and this could cause potential security bottlenecks. 

.

Hello Christopher Kennedy did you come to any solution in regards to this issue?

We are experiencing the same problems. Web Widget stores conversation history in Cookies (saved across subdomains) and local storage (not shared across subdomains). Is there any way to retain the conversation history across sub domains?

In regards to authentication, we are planning to implement it, but there would be the same issue. 
Users who are authenticated on one domain, might not be authenticated when they switch to the sub-domain... or would they? Unfortunately the documentation in this regard is very scarce. (I have read all the articles about end-user authentication for messaging, to no avail)