Skip to content
This repository has been archived by the owner on Jun 30, 2022. It is now read-only.

Shared Token? #721

Closed
ghost opened this issue Feb 7, 2019 · 2 comments
Closed

Shared Token? #721

ghost opened this issue Feb 7, 2019 · 2 comments
Assignees

Comments

@ghost
Copy link

ghost commented Feb 7, 2019

Project
Virtual Assistant (version from 2018-12-04)

Description
Time: 11:00 (CEST)
Location: Germany
I use my VA with channel WebChat.
After entering 'Send e-mail to XY' I was asked to login to a Microsoft account, what I did.
I got a verification code in a browser window, which I entered into the chatbot.
I refreshed the web page.
I successfully sent a email via VA.

Time: 16:00 (CEST)
Location: US
Another person on another device, also entered 'Send e-mail to XY', but was not asked to login. Instead the other person had access to my Outlook365 account, e.g. to show the task list or to send an email on my behalf.

Expected behavior
Every user have access only to his/her own Office365 account.

Questions

  • Are the security token maintained and cached on the server side?
  • It is a known bug, which was fixed in later versions?
@darrenj
Copy link
Contributor

darrenj commented Feb 7, 2019

HI @David201406,

This is likely the webchat issues whereby it defaults to a user-id of "default". once you signin the Azure Bot Service does securely store a token against your userid for future refresh/use. As webchat on two machines is using the same userid you can see this scenario. This is highlighted here

This has been fixed: microsoft/BotFramework-WebChat#1612 and will be in the next release but you should be able to reference a more recent build from here on your script tag.

Let me know if this helps

@darrenj
Copy link
Contributor

darrenj commented Feb 7, 2019

you can type signout or /event:{Name:"IPA.ResetUser"} to remove any tokens/state too

@darrenj darrenj self-assigned this Feb 7, 2019
@darrenj darrenj closed this as completed Feb 18, 2019
@lauren-mills lauren-mills removed Status: In Progress This work item in underway. Status: Committed This has been confirmed for the next release. Type: Suggestion labels Jul 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants