调用getUserIdentityTokenAsync()返回空令牌 [英] Call to getUserIdentityTokenAsync() returning a null token

问题描述

我们在生产环境中有一个外接程序，对于某些用户，对getUserIdentityTokenAsync()的调用失败，并返回null令牌.

We have an add-in in production where, for certain users, the call to getUserIdentityTokenAsync() fails and returns a null token.

响应为

"Status" = "failed", 
"Error" = {message: "An internal error has occurred", name: "Internal Error"}

有人知道什么会导致这种类型的故障吗?某些用户总是会收到错误，而我们从未在本地或开发过程中见过该错误.

Would anyone know what could cause this type of failure? Certain users always get the error, and we have never seen the error locally or during development.

这似乎仅适用于桌面Outlook用户.通过浏览器使用加载项时，我们看不到用户有任何错误.

It seems to happen only for desktop Outlook users. We have not seen any errors for users when using the add-in via the browser.

推荐答案

我正在根据Outlook加载项团队在评论中的答复来更新答案.

I am updating the answer based on a response from the Outlook Add-ins Team in the comments.

在MSI版本中:针对Exchange 2013的16.0.4540.1000至16.0.4585.1000，GetUserIdentityToken不起作用.在之前的MSI版本，16.0.4540.1000/15.0.4931.1000和16.0.7813.1000之前的C2R版本中-调用GetUserIdentityTokenAsync和MakeEwsRequestAsync会导致失败

In MSI versions: 16.0.4540.1000 to 16.0.4585.1000 against Exchange 2013, GetUserIdentityToken did not work. In MSI versions before, 16.0.4540.1000 / 15.0.4931.1000 and C2R versions before 16.0.7813.1000 - calling GetUserIdentityTokenAsync along with MakeEwsRequestAsync would cause a failure

就我而言，大多数遇到问题的用户都在上面发布了客户端版本号.升级他们的Outlook版本可以解决此问题.

In my case, most of the users experiencing the problems had the client version numbers posted above. Upgrading their outlook version solved the issue.

这篇关于调用getUserIdentityTokenAsync()返回空令牌的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！