search

microsoft / BotFramework-WebChat

A highly-customizable web-based client for Azure Bot Services.
https://www.botframework.com/
MIT License
1.6k stars 1.54k forks source link

Web Chat control embedded in HTML with iframe cache The state management objects for the conversation and user state #2411

Closed ramcaltech2019 closed 5 years ago

ramcaltech2019 commented 5 years ago

Bot framework SDK version 4.0 with NodeJS Web Chat control code embedded taken from azure portal:

<iframe src='https://webchat.botframework.com/embed/uvschatbot-003?s=YOUR_SECRET_HERE'  style='min-width: 400px; width: 100%; min-height: 500px;'></iframe>

the control cached the the state management objects for the conversation and user state with the server powered by IIS in azure I display the username captured for the first user and all the request from different users see the same name, if I modify the web.config this action restarts IIS and the cache is flushed.

Even with this bot framework code the Web Chat control caches in IIS 

// For local development, in-memory storage is used.
// CAUTION: The Memory Storage used here is for local bot debugging only. When the bot
// is restarted, anything stored in memory will be gone.
const memoryStorage = new MemoryStorage();
conversationState = new ConversationState(memoryStorage);
userState = new UserState(memoryStorage);

This is a annoying bug that needs to be fixed.

Thank you in advance. Jose Ramirez

tdurnford commented 5 years ago

@ramcaltech2019 Are you generating a DirectLine Token for each conversation or are you just using your Web Chat Secret? If multiple conversations are sharing the same user data, it usually indicates that all of the users are sharing the same user id.

tdurnford commented 5 years ago

As I mentioned, if two conversations share the same user id, they will share the same user data in storage. Currently, the iFrame saves the user id in session storage, so you have to close and restart the browser to start a new conversation with a new user id. The development team is aware of the issue and is working towards getting it resolved. In the meantime, you can host your own instance of Web Chat instead of using the iFrame. Take a look at our samples for help getting started.

ramcaltech2019 commented 5 years ago

@ramcaltech2019 Are you generating a DirectLine Token for each conversation or are you just using your Web Chat Secret? If multiple conversations are sharing the same user data, it usually indicates that all of the users are sharing the same user id.

tdurnford: I am using only the Web Chat Secret, not a DirectLine Token for each conversation, what I want to accomplish is to cache the unique user id for each user, ask the user for a name, save the name using the unique user id and when the user comes back retrieve the name and welcome the user, I use the bot framework sdk 4 with nodejs, the user id is generated in the activity.from.id, the problem is that it generates a unique id every time the user start over the conversation so I can't use it as a unique key.

Your help is greatly appreciated. Thank you

ramcaltech2019 commented 5 years ago

As I mentioned, if two conversations share the same user id, they will share the same user data in storage. Currently, the iFrame saves the user id in session storage, so you have to close and restart the browser to start a new conversation with a new user id. The development team is aware of the issue and is working towards getting it resolved. In the meantime, you can host your own instance of Web Chat instead of using the iFrame. Take a look at our samples for help getting started.

thank you! will look into hosting my own instance of Web Chat