实时连接认证令牌在Azure移动服务使用（REST） [英] Live Connect Authentication Token for use on Azure Mobile Services (REST)

问题描述

我有一个简单的Windows窗体应用程序尝试实时连接和Azure的移动服务。不是Windows 8应用现代

I have a simple Windows Forms Application to try Live Connect and Azure Mobile Services. Not a Windows 8 Modern App.

我试图利用对实时连接一些示例代码，并已经能够获得登录部分做工精细。最后，我在登录后得到的access_token。

I'm trying to make use of some sample code for Live Connect and have been able to get the sign-in part to work fine. In the end I get an access_token after signing in.

在同一个Windows的移动服务端窗体应用程序，我试图使用REST登录。但是，我seeem得到一个401未授权的响应，因为身份验证令牌的签名格式不正确或不同的密钥签署的

On the Mobile Services side in the same Windows Forms Application, I'm trying to use REST to login. However, I seeem to get an "401 Unauthorized" response because "The authentication token's signature was malformed or signed by a different key"

智威汤逊似乎有两个。在令牌中。
SWT似乎有'/'，'+'和'='

JWT seem to have two '.' in the token. SWT seem to have '/', '+' and '='

有没有办法，我需要做的转换？

Is there a conversion that I need to do?

有没有配置实时连接，使返回的认证令牌是智威汤逊（或任何移动服务预计，）？

Is there a way to configure Live Connect so that the authentication token returned is JWT (or whatever Mobile Services expects)?

我的方式已经检查两个实时连接和移动服务客户端的秘密，他们是正确的。

I've check the client secret on both Live Connect and Mobile Services, and they are correct.

推荐答案

正如@carlosfigueira指出，在Live Connect开发中心，您的应用需要在重定向域字段的东西。它可以是一个虚拟的URI

As pointed out by @carlosfigueira, in the Live Connect Developer Center, your app needs to have something in the redirect domain field. It can be a dummy URI.

这是一个答案在这里Corroberated：的 http://social.msdn.microsoft.com/Forums/en-US/messengerconnect/thread/4a110db0-6468-44fb-9152 -771987ded050

Corroberated by an answer here: http://social.msdn.microsoft.com/Forums/en-US/messengerconnect/thread/4a110db0-6468-44fb-9152-771987ded050

这篇关于实时连接认证令牌在Azure移动服务使用（REST）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！