Skip to content
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.

Info on setting up VSTS integration #41

Open
TonyHernandezAtMS opened this issue Jan 11, 2018 · 1 comment
Open

Info on setting up VSTS integration #41

TonyHernandezAtMS opened this issue Jan 11, 2018 · 1 comment

Comments

@TonyHernandezAtMS
Copy link

I've registered an App with VSTS. I've updated the environment variables with the client id and key. Running "log in" works until I open the pop-up for client auth. I get "Exception of type 'Microsoft.VisualStudio.Services.Web.Profile.Controllers.DelegatedAuthorizationException' was thrown."

Ideas?

@jotrick
Copy link
Contributor

jotrick commented Jan 11, 2018

For starters, I would say the VSTS integration is all but deprecated in this sample. It has stuck around as a sort of legacy area for a few bits of code that are more meant to be "read rather than run". The go forward approach is to use some of the new features Teams is offering (that have not QUITE gotten all the way to the public ring, so developer preview is required). This is why there are no steps documented on how to actually get that bit running. That being said, it doesn't mean the code shouldn't run, but it does mean it may be harder to debug it as things around it have changed. One step you hadn't mentioned would be registering the callback URL with the VSTS app you have set up. As for why you are trying to run it, are you curious to just get every part of the app running or are you looking for an example of auth? If it is the latter, I would recommend looking at the static tabs offered by this app along with this blog post: https://techcommunity.microsoft.com/t5/Microsoft-Teams-Blog/Authentication-SSO-and-Microsoft-Graph-in-Microsoft-Teams-Tabs/ba-p/125366

Also, for bot auth, there is a lightweight example of the new sign in card action in the branch "bot-sign-in-example" that uses the AAD auth mentioned above. This sign in action is listed in the HeroCardDialog of that branch. The reasons why we have not documented these things yet are because the feature is still new, may be susceptible to change, and because of this, the examples are not quite to depth we would like them to be.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants