Bot not responding after updating secret value in azure AD (Microsoft entra)

[samthrusha123]

Is it an issue related to Adaptive Cards?

No

Is this an accessibility issue?

No response

What version of Web Chat are you using?

Latest production

Which distribution are you using Web Chat from?

Unrelated

Which hosting environment does this issue primarily affect?

Web apps

Which browsers and platforms do the issue happened?

No response

Which area does this issue affect?

Others or unrelated

Which theme pack does this issue affect?

I did not test it on other theme packs

What is the public URL for the website?

No response

Please describe the bug

Bot not responding after updating secret value in azure AD (Microsoft entra). Even though secret is proper it is giving invalid client secret error in deployed environment. In Local it is working fine with same credentials.

In application insights it's giving

https://login.microsoftonline.com/botframework.com/oauth2/token - This call is giving 401

Do you see any errors in console log?

Getting this error in console when claling with directline token
{
  "error": {
    "code": "BotError",
    "message": "Failed to send activity: bot timed out"
  },
  "httpStatusCode": 504
}

How to reproduce the issue?

Update client secret & restart

What do you expect?

Solution why bot is not responding

What actually happened?

In Azure AD secret has been expired so I updated the secret & restarted the app by updating in appsettings. It didn't work, I compared UAT & PROD environemtn. UAT bot is multi tenant PROD bot is single tenant. So I've deleted this bot & create new bot with multi tenant mapped to same AD app & same name. Still not working.

Do you have any screenshots or recordings to repro the issue?

No response

Adaptive Card JSON

Additional context

No response

[stevkan]

This doesn't sound like it is a Web Chat issue. Can you tell me which SDK you are using so I can have this assigned to the correct repo?

As for the issue you are experiencing, I have a few questions:

• In addition to which SDK, which version of it are you using?
• Where is the secret being stored and accessed from when the bot is run locally?
• Where is the secret being stored and accessed from once the bot is deployed?

So I've deleted this bot & create new bot with multi tenant mapped to same AD app & same name.

• I'm confused by what you mean in this statement. Are you working with a completely new bot and AD app registration? Or did you only create a new bot and are trying to align it to the app registration that belonged to the first / original bot?