OAuthPrompt should provide the ability to cancel itself

[EricDahlvang]

Issue

Example Scenario-
User says : “login”
Bot says : OAuthCard
User says : “I want to enter a number”

Expected behavior – OauthPrompt completes and “I want to enter a number” Activity is handled by the next Prompt/Dialog in the Dialog stack.

Tracking Status

Dotnet SDK
microsoft/botbuilder-dotnet#4395

• PR
• Merged

Javascript SDK
microsoft/botbuilder-js#2651

• PR
• Merged

Python SDK
microsoft/botbuilder-python#1320

• PR
• Merged

[dcr]

[stevengum]

@swagatmishra2007 and @carlosscastro can you provide more context on this ask? Interruptions and cancellations are already possible at the DialogContainer level, which is likely where you'd want to handle the interruption.

The enhanced OAuthPrompt wouldn't know about the other Prompts or Dialogs being used in the DialogContainer, nor does it have the necessary logic built-in to disambiguate which Dialog it should call.

The current model is:

1. User initiates OAuth flow
   a. Activity likely goes through DialogContainer (e.g. DialogManager, ComponentDialog)
   b. DialogManager begins OAuthPrompt, sends card to user

2. User interrupts/cancels OAuth flow "I want to enter a number"
   a. Activity routes to DialogManager
   b. DM determines next dialog to call
   c. DM replaces current OAuthPrompt with appropriate Dialog via DialogContext.ReplaceDialogAsync (.NET, JS, Py)

[cleemullins]

Discussion with @clearab, @tacri , Sid, and Eric - Andrew will write a spec for this before any next steps.

[clearab]

Best we can come up with is to add a flag to OAuth prompt and document needing to set it.

[clearab]

JS is in PR