Unanswered

Silent failure at authentication step

(0) Share

Report

Posted on by tdixon

I wrote a big question about this with pictures and links to resources, but it was deleted as 'spam'. So I'm going to try and ask again with less of all that in hopes it doesn't get deleted this time.

Long story short, I'm trying to set up a bot using PVA with manual authentication. We only want to use it with Teams, but don't want to use the 'teams only' authentication because we need access to the auth token. I've done my best to follow the 4 different MS documents that talk about setting this up, but for some reason while it works fine in the test panel of the PVA site, when I try it in teams it does everything that occurs before the authentication step then stops without further output.

Categories:

Building Copilot Studio chatbots in Microsoft Teams

I have the same question (0)

All responses (25)

Answers (0)

Kamrani on at

Like (0)

Report

Hi tdixon- I tested a bot with manual auth in Teams, and when I ping it, it logs me in. This is the output I get using a generic bot that is created using PVA:

Not sure why your original post was deleted. What do you see in Teams? Thx

Was this reply helpful? Yes No
tdixon 28 on at

Like (0)

Report

I don't have required login turned on, since when I did have it turned on, I was getting basically nothing on the Teams end.

Here's some shots of my setup:

Here's the login topic. I have 'v3' in there so I can tell that the details have actually changed. Sometimes it takes a long time for the PVA to publish, it seems.

And here's what I see in Teams:

It just stops after the first message. It's really frustrating that I can't find anywhere to debug the conversation flow, and maybe get some kind of error message.

Was this reply helpful? Yes No
tdixon 28 on at

Like (0)

Report

Here's some details from the app registration in case there's something obvious I'm missing here.

Was this reply helpful? Yes No
Kamrani on at

Like (0)

Report

I noticed that the Tenant Id field is empty in your case. Add that in and enable Require users to sign in. Test to see if that fixes the issue.

Was this reply helpful? Yes No
tdixon 28 on at

Like (0)

Report

I copied my tenant ID from the app registration summary page, and turned on require users to sign in, as you suggested. It doesn't seem to have helped.

Was this reply helpful? Yes No
Kamrani on at

Like (0)

Report

In the Azure Portal, under Expose an API, can you check to see if you have the values shown below in red? The last value for Client Id at the bottom must be the same as mine. These are for Teams Web and App clients. This help topic goes over it in detail.

Was this reply helpful? Yes No
tdixon 28 on at

Like (0)

Report

Yes, that's one of the documents I read. I had those client IDs in there already. I did have the scope set to admin only, but changing it to admin and users doesn't seem to have changed anything.

Was this reply helpful? Yes No
Kamrani on at

Like (0)

Report

Does the bot work in PVA portal?

Was this reply helpful? Yes No
tdixon 28 on at

Like (0)

Report

I had to set the app registration back to multitenant. I had set it to single tenant earlier as part of my own testing.

But yes, it works just fine in the PVA portal, once the app registration is set to multitenant. It shows a button to log in, I get a popup tab with a code, which I paste back into the chat and I am logged in successfully.

Was this reply helpful? Yes No
Kamrani on at

Like (0)

Report

Could you republish your bot in PVA portal, uninstall it from Teams, and reinstall it?

Was this reply helpful? Yes No