Issue
In the Microsoft BotBuilder family, the .Net NuGet package Microsoft.Bot.Connector.DirectLine is not Open Source and does not have a GitHub repo, so I open this issue here.
In the bot service documentation, it says that if an app has an expired token (too late to be renewed) in the client side, it should ask the server-side of the application to create a new token for the current conversation, based on the secret (that the server-side has but not the client-side) : Reconnect to conversation.
The typescript DirectLine SDK has the documented "reconnect" function which updates the new token and new websocket stream url.
The .Net C# NuGet client SDK does not have a reconnect function which accepts the new token and websocket stream url like the TypeScript SDK does. It only proposes to use the current expired token to create a new one itself. It makes it more difficult to implement bot client in C#.
Proposed change
Adding to the .Net client SDK the feature supported by the TypeScript SDK.
Ideally, open sourcing the client NuGet package too.
Component Impact
The .Net NuGet package Microsoft.Bot.Connector.DirectLine.
Customer Impact
Not able to follow the documentation for expired tokens when creating .Net bot client which uses a token and does not embed the secret itself.
Tracking Status
Dotnet SDK
[dcr]
Issue
In the Microsoft BotBuilder family, the .Net NuGet package Microsoft.Bot.Connector.DirectLine is not Open Source and does not have a GitHub repo, so I open this issue here.
In the bot service documentation, it says that if an app has an expired token (too late to be renewed) in the client side, it should ask the server-side of the application to create a new token for the current conversation, based on the secret (that the server-side has but not the client-side) : Reconnect to conversation.
The typescript DirectLine SDK has the documented "reconnect" function which updates the new token and new websocket stream url.
The .Net C# NuGet client SDK does not have a reconnect function which accepts the new token and websocket stream url like the TypeScript SDK does. It only proposes to use the current expired token to create a new one itself. It makes it more difficult to implement bot client in C#.
Proposed change
Adding to the .Net client SDK the feature supported by the TypeScript SDK.
Ideally, open sourcing the client NuGet package too.
Component Impact
The .Net NuGet package Microsoft.Bot.Connector.DirectLine.
Customer Impact
Not able to follow the documentation for expired tokens when creating .Net bot client which uses a token and does not embed the secret itself.
Tracking Status
Dotnet SDK
[dcr]