Audience and ConversationReference is required for Proactive Messaging non-channel recipients

[stevengum]

Issue

In proactive messaging scenarios, bots may now message either a Channel or another bot.

For proactively messaging a channel, storing the ConversationReference is sufficient because the correct Audience ("https://api.botframework.com") is hardcoded into the Botbuilder SDKs.

For proactively messaging another bot, the sender must store the ConversationReference and the correct Audience.

Proposed change

The proposed solution is to create a SkillsConversationReference subclass and store the Audience on this new class.

Component Impact

Potentially SkillConversationIdFactoryBase, add new class to Microsoft.Bot.Builder (in Skills/).

Tracking Status

Dotnet SDK

• PR ([Skills] Refactor BFAdapter Auth, Add support for proactively messaging non-channel recipients botbuilder-dotnet#3409)
• Merged

Javascript SDK

• PR
• Merged

Python SDK

• PR
• Merged

Samples

• PR (80.skills-simple-bot-to-bot)
• Merged

Docs

• PR
• Merged

[dcr]

[stevengum]

microsoft/botbuilder-dotnet#3386

[stevengum]

@johnataylor and I are strongly leaning towards not subclassing and making the audience (or OAuthScope) a required parameter in ContinueConverastionAsync.

[stevengum]

Closing, this was released with v4.8.