问题描述
我们有一个使用bing-ads-java-sdk的AWS lambda。
2018-04-06它开始失败并出现错误：
$
POST https://login.live.com/oauth20_token.srf
{
  "error"："invalid_grant"，"
  " error_description"："用户无法通过身份验证或授权已过期。用户必须首先登录并在必要时授予客户端应用程序访问所请求范围的权限。"
}
认为这是一个标准的refresh_token是我们更新它的陈旧错误。但是，它没有解决问题。我们现在已经将库jar升级到版本microsoft.bingad 11.5.8.1，并通过向Microsoft live apps注册一个
的第二个应用程序来确认问题与原始client_id无关。
奇怪的是，只有将lambda部署到AWS时才会发生故障。在我们的本地环境以及我们的travis CI中，包含执行实时呼叫的测试的套件成功通过（我们已经手动测试了两个应用程序验证详细信息，并且成功获得了
）。
我们将非常感谢任何帮助或指导。
We have an AWS lambda which makes use of the bing-ads-java-sdk.
On 2018-04-06 it began to fail with the error:
POST https://login.live.com/oauth20_token.srf
{
"error": "invalid_grant",
"error_description": "The user could not be authenticated or the grant is expired. The user must first sign in and if needed grant the client application access to the requested scope."
}
Thinking this was a standard refresh_token is stale error we updated it. However, it did not fix the issue. We have now upgraded the library jar to version microsoft.bingad 11.5.8.1 and confirmed the issue is not with the original client_id by registering a second application with Microsoft live apps.
Curiously, the failure only occurs when the lambda is deployed to AWS. In our local environments as well as our travis CI the suite which includes a test that performs a live call passes successfully (we have tested both application auth details manually with success too).
Any help or guidance would be greatly appreciated.
推荐答案
这篇关于无法对用户进行身份验证或授权已过期的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！