Azure RemoteApp协议更新 [英] Azure RemoteApp Protocol Update

查看:94
本文介绍了Azure RemoteApp协议更新的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我已经开始研究Azure RemoteApp预览功能,看看我是否可以在FreeRDP中实现支持。我已经从https://www.remoteapp.windowsazure.com/ClientDownload/WindowsDemo.aspx安装了演示客户端并开始使用它。

I have started looking into the Azure RemoteApp preview feature to see if I could implement support in FreeRDP. I have installed the demo client from https://www.remoteapp.windowsazure.com/ClientDownload/WindowsDemo.aspx and started playing with it.

客户端似乎正在获取.rdp文件使用类似于MS-RDWR的协议,但我无法确保此时确实是MS-RDWR。我在文件系统上找到了本地缓存的.rdp文件,并尝试使用mstsc启动它们而没有
成功,与FreeRDP相同。使用mstsc,我收到密码提示,但输入通常与azure一起使用的凭据不起作用。在检查.rdp文件的内容之后,我可以找到一些未记录的值和选项,我想知道更多关于它们以及它们如何与协议相关的信息。

The client appears to be fetching .rdp files using a protocol similar to MS-RDWR but I have no way of making sure that it is indeed MS-RDWR at this point. I found the locally cached .rdp files on the file system and tried launching them with mstsc without success, same with FreeRDP. With mstsc, I'm getting the password prompt, but entering credentials normally used with azure doesn't work. After inspecting of the content of the .rdp files, I could find a few undocumented values and options which I'd like to know more about and how they related to the protocol.

gatewaybrokeringtype:i:1

gatewaycredentialssource:i:6

评论:s:DoNotChangeOrRemoveAnyOfTheAbovePropertiesUnlessAbsolutelyNeeded

gatewaybrokeringtype:i:1
gatewaycredentialssource:i:6
comments:s:DoNotChangeOrRemoveAnyOfTheAbovePropertiesUnlessAbsolutelyNeeded

稍后文件中有" redirectdirectx:I:1"这是一个老选项,我从来没有弄清楚它在做什么。还有新选项"eventloguploadaddress:s:https://www.remoteapp.windowsazure.com:444 / webUpload?mohoroId = b72e4297-5d1a-4439-9ac3-37f75aeb4f0a""
是自描述的。

Later in the file there is "redirectdirectx:i:1" which is an old option that I never figured out what it was doing. There is also the new option "eventloguploadaddress:s:https://www.remoteapp.windowsazure.com:444/webUpload?mohoroId=b72e4297-5d1a-4439-9ac3-37f75aeb4f0a" which is self-descriptive.

客户端附带adal.dll,它看起来像Active Directory身份验证库(ADAL)的本机版本。 Gateway Credentials Source的值6未记录,最后记录的值为5.我找不到Gateway
Brokering Type的文档,我找到的所有google都是对值0使用但不是值1的引用。

The client ships with adal.dll, which looks like a native version of the Active Directory Authentication Library (ADAL). Value 6 for the Gateway Credentials Source is undocumented, the last documented value being 5. I could not find documentation for Gateway Brokering Type, and all I could find I google was references to value 0 being used but not value 1.

看起来Azure RemoteApp可能正在使用一种新形式的网关身份验证,我现在只能使用Active Directory身份验证库来猜测。

It looks like Azure RemoteApp may be using a new form of gateway authentication, which I can only guess to be done using the Active Directory Authentication Library at this point.

知道这一点,我的问题是:Azure RemoteApp支持应该有哪些协议更新和要求?它是否需要RDP8.1 RemoteApp增强功能?是否需要RDP8网关协议(支持UDP的协议)?是否
是Azure RemoteApp的新身份验证协议(新值6)?

Knowing this, here is my question: what kind of protocol updates and requirements should be expected for Azure RemoteApp support? Does it require the RDP8.1 RemoteApp enhancements? Is the RDP8 gateway protocol (the one with UDP support) required? Will there be a new authentication protocol for Azure RemoteApp (the new value 6)?

谢谢!







推荐答案

嗨Marc-Andre,

Hi Marc-Andre,

谢谢你的支持。问题 我可以帮助你。 让我研究一下你,我会尽快回复。

Thank you for your questions.  I can help you with these.  Let me research for you and I'll reply as soon as possible.


这篇关于Azure RemoteApp协议更新的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆