Botbuilder-js: Mask User Input

Created on 22 May 2018 · 5Comments · Source: microsoft/botbuilder-js

During a Dialog in Bot-Framework, adding the feature of masking the user input(response to Prompts) would be very very helpful.

Source

saranyuavh

Most helpful comment

I think this is something that has to be implemented by the channels itself. (so WebChat and Microsoft Teams). In my previous reply I already linked to a possible solution for the webchat, where they also have a discussion.

Especially on Microsoft Teams, I believe there are better options for authenticating your users instead of sending a plain text password to your bot. I would recommend using a sign in card for this which sends you to an external website to perform the login or even better use OAuth to implement your custom login provider.

iMicknl on 22 May 2018

👍3

All 5 comments

Why and on which channel? Do you mean that you want to have the user input masked in the WebChat, so like a password field? At the moment there is a discussion about this in another repository. https://github.com/Microsoft/BotFramework-WebChat/pull/976. However I wouldn't recommend that.

Or do you want to filter out credit card information (for example) from the text response. In order to do something like that, just writing a custom middleware with some regexes should do the job already.

iMicknl on 22 May 2018

I have connected a database to the bot which has users database and users can login though the bot dialog itself where I am using prompts.text, therefore, I want to mask the user input while the user is responding to the prompt "builder.Prompts.text("Enter your Password")". Once user is authenticated, a query can be raised according to his question or selected suggestion. Currently, I am developing the bot and testing it on the emulator and I will later deploy it as a Bot in MS Teams.

forgithub

I want to mask the input present in the attached screenshot.

saranyuavh on 22 May 2018

iMicknl on 22 May 2018

👍3

Thanks @iMicknl ... Agree on all accounts. This is something that would have to be implemented by the channels and you should probably use oAuth instead.