BotAuth is obsolete?

[dnws]

BotBuilder since release 3.15.1.0 supports generic OAuth flows and AADv1/v2 authentication methods out of the box. There are examples for each auth flow in official documentation. Integrated flows are also capable of making all the verifications in the background. This project even being presented on Build 2018 seem to be abandoned.

@mattdot should it be discontinued and marked as such?

[josephktcheung]

@dnws I want to use built-in OAuth in bot service too but the lack of documentation makes it impossible for me to implement the flow with Auth0. Please read the comments in the documentation page where people are complaining about the lack of documentation, examples and problems like refreshing tokens not working etc.

BotAuth can serve as an alternative to people who are not yet satisfied with the bot service OAuth implementation, until most questions in the official documentation comments section are answered,
documentation is more polished and more examples are provided.

[rgarita]

I had issues with BotBuilder OAuth cards on teams, so I'm back on this one.......

[EricDahlvang]

@rgarita What were the issues you ran into with OAuth cards on teams?

[belcsy]

I have some issues with the BotBuilder OAuth card as well.

The error i constantly get is that 'Parameter "url" must be a string, not undefined' in the Bot Emulator. I have tried to change the 'value: undefined' to a fixed value in OAuthCard.js, but it is not working as well. I couldn't find any documentation on where exactly i should provide a url...

I bounced back to BotAuth, which is now working better for me

[rgarita]

@EricDahlvang

Basically I cannot click on it... It does work on the webchat version but not on teams

Raul

[dnws]

Closing this issue, as library is now officially marked as obsolete in commit 0988df6.