Botframework-sdk: POST refresh access token failed with status code: 400

[khakiali]

Thanks for creating the framework! I am trying to follow this and create the generic bot, but am having issues trying to get the emulator recognize my bot. I have attached the webconfig and error message shown by the emulator.

[eanders-MS]

Hi @khakiali, Sorry you're having this problem. Please check your computer's date and time settings. Our authentication scheme requires these to be accurate to within five minutes.

[khakiali]

Hi Eric,
Thanks for the reply. However i do not think that is the root cause.
My date/time is aligned with the authentication. please see attached.

[khakiali]

apologies did not mean to close issue :).

[khakiali]

its ok - i managed to resolve it. I was using an older version of the template, this conflicted with the new version of the bot!

[NotTooReact89]

Hi can you please shed some light on what you meant by older version of the template?

[khakiali]

Hi,
I was using an earlier version of the SDK which had an older version of the web.config file. The appears to have authentication between that and the emulator. A good way to tell whether you have an older version is that the new version has MicrosoftAppID and MicrosoftAppPassword keys instead of just simply appid and app password keys within the appsettings of the web.config file,

[jorge-sanz]

@khakiali Same problem here. How did you solve it?

[felipeq]

Same here. Bumping.

[saurabhabh]

Guys check this - https://docs.botframework.com/en-us/support/troubleshooting-bot-framework-authentication/ . I had the same issue. Following the steps in this url fixed it.

[NotTooReact89]

When you use localhost you don't need to specify the credentials in the emulator and in the code too. Credentials come to use when you deploy it to Azure.

[McGern]

@saurabhabh that link is dead for me.

I am having a similar issue using the bot on azure running through the emulator. It works without credentials, but not with the credentials (in the emulator). Have MicrosoftAppId and MicrosoftAppPassword set in the web.config and have taken the id and password from the application registration portal. Wanting to get it working through webchat, but at this point can't even see it in the emulator.

[saurabhabh]

I think you need to publish your bot so as it could make use of the credentials. For the local emulator which is just for testing you don't need credentials.

[McGern]

For testing with directline etc, you need an app id and password. This is before the bot is published.

[adekola]

@McGern: here's the correct link.. https://docs.microsoft.com/en-us/bot-framework/troubleshoot-authentication-problems. I guess you must have solved your issue by now anyways.

[McGern]

Thanks for the link.

Think I ended up having to remove something in that was in the register method of the bot. It was bypassing the builtin authentication somehow and needed to do it manually (that led to a host of other issues). I am not sure if what I have is right but it seems to work for now.

[lchinitz]

Is anyone else experiencing this problem now, out of the blue? I have a bot running, and have had it running, for months with no issues. It's using botbuilder 3.6.0, and there have been no changes to the code that would cause this. In the morning it was working, and suddenly it started throwing this error about refresh access token failed with status code 400. Is anyone else seeing this, or does anyone have any thoughts? Troubleshooting the authentication problem hasn't helped me. My ID and PWD are correct (I didn't change them anyway).

[Tomasz-Silpion]

Up, same here. Happened with no reason today killing all my bots running for weeks without issues.

Tried so far:

• Regenerating appId and appPassword
• Updating botbuilder node package

Nope, I'm using 3.8.4 already released 2 months ago https://www.npmjs.com/package/botbuilder

[joshftx]

Same here.
[Tue Jul 25 2017 15:18:13 GMT-0400 (EDT)] ERROR Error: Refresh access token failed with status code: 400

[isabelacmor]

Also having this issue, since about 30 mins ago. Tried

• regenerating appId and appPassword
• creating new bot and using that one's appId and appPassword
• updating node packages

[nsantini]

same here on 3.8.4. Worked yesterday...

[jazzedge]

Got exactly the same problem. Bot was working this afternoon. Now the 400 error has appeared. Haven't changed the Emulator or anything else.

[mmalaiarasan-conga]

Same here. Test from bot framework dashboard isn't working either.

[nsantini]

I can confirm I get the same issue using WebChat and Skype channels. So no channel specific (ie webchat secret), its the bot itself

[lchinitz]

Does Microsoft monitor this page? Or is there some way of telling them about this? (Just asking if anyone knows, because I don't.)

[isabelacmor]

I'm trying to find out who works on Bot Framework to ping them internally.

[Tomasz-Silpion]

They already know about it https://github.com/Microsoft/BotBuilder/issues/3197

[jazzedge]

Do we get service credits? :-)

[ahsendinc]

Same here! It was working yesterday but today it is not working with credentials, it is not channel specific, it does not work for neither webchat nor skype. Also, for emulator, it is the same issue if the credentials are given.

[IanLawrence]

There is an error with Microsoft’s Authentication service it seems

[agarwalarun17]

I also stuck with the same error. It was working before 5 hours, but now not working. It works if remove the APPID and PASSWORD...

[advl03]

Same problem here. We are suffering this problem since 8 PM CEST. I will continue monitoring this thread and the thread where the issue has been opened: https://github.com/Microsoft/BotBuilder/issues/3197
Will post here if our bots start working again.

[lchinitz]

I think the authentication server is back online. My bot has started responding again.

[advl03]

Yes, confirmed as per the latest comment in https://github.com/Microsoft/BotBuilder/issues/3197 and with my two bots

[debnathSD]

Yes. Same problem happening here again. From last 2 hours

[adekola]

Is it related to this https://azure.microsoft.com/en-us/status/?

On Fri, Apr 6, 2018 at 1:24 PM, Sourav Debnath [e-mail]
wrote:

Yes. Same problem happening here again. From last 2 hours

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/BotBuilder/issues/1938#issuecomment-379225253,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACm3j6zTaVs9OOvDKhjhTw1QjI070mHHks5tl1CJgaJpZM4LYmkN
.

--
Adekola ADEBAYO

[anvad]

I had the same issue till about 30 minutes ago. Bot authentication was failing with "Error: Refresh access token failed with status code: 400" until I restarted my bot web server, My bot service on Azure is in west central US and the outage in azure referred to Europe and East Asia. Possibly the bot service depended on these other regions or the outage affected more regions than they detected.

[EricDahlvang]

@debnathSD @adekola @anvad

Please refer to https://github.com/Microsoft/BotBuilder/issues/4432

There was an issue with Azure AAD last night that affected bots. It has been resolved. If your bots are still experiencing issues, please restart the service.

[Heromaimx]

Refresh access token failed with status code: 401

[Heromaimx]

Refresh access token failed with status code: 401

[Heromaimx]

Refresh access token failed with status code: 401

[solidcloudio]

Guys check this - https://docs.botframework.com/en-us/support/troubleshooting-bot-framework-authentication/ . I had the same issue. Following the steps in this url fixed it.

Dead link now..