如何正确准备 Citrix ICA 客户端对象实例以使用 Citrix Access Gateway 成功连接到场?
我正在使用 Citrix ICA 客户端对象 API 以编程方式建立与已发布应用程序的连接。通常,它就像订阅多个事件、向对象提供 ICA 文件(通过 LoadIcaFile 方法)并调用 Connect 方法一样简单。
但是,对于 ICA 客户端 12.1 或更高版本,如果使用 CAG 并且 ICA 文件的地址字段包含加密令牌而不是服务器 IP/名称,则此方法会导致立即断开连接事件。如果 ICA 文件包含直接服务器地址(我认为这意味着未使用 CAG),则相同的方法适用于较旧的客户端 (10.x)或
如果任何人在针对 Citrix Access 的编程会话启动中取得成功网关环境成功与 ICA 客户端 12.1 或更高版本配合使用,请分享它是如何完成的。
注意:从实践来看,我对 Citrix 服务器端的理解非常有限 - 我相信我遇到过 ICA 文件,其中包含来自 Web Interface 到使用以下任意项的场的神秘地址字段:citrix 访问网关、citrix 安全网关、citrix netscaler
I am using Citrix ICA client object API to establish a connection to published applications programmatically. Typically, it is as simple as subscribing to a number of events, feeding the object with an ICA file (via LoadIcaFile method) and invoking Connect method.
However, with ICA clients 12.1 or higher, this approach leads to immediate disconnect event in case if CAG is used and ICA file's Address field contains a cryptic token instead of server IP/name. The same approach works fine with an older client (10.x) or if ICA file contains direct server Address (which I assume means CAG is not used)
If anyone had success in programmatic session launches against Citrix Access Gateway environments successfully working with ICA client 12.1 or higher, please share how it was done.
NOTE: my understanding of Citrix server side is very limited, from practise - I believe I met with ICA files containing cryptic Address field coming from Web Interface to farms using any of the following: citrix access gateway, citrix secure gateway, citrix netscaler
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
这里不太可能有任何其他解决方案,所以我认为我的最新评论是一个答案:
ICA 客户端 13.1 连接得很好(就像客户端 10.200 那样)
因此与 CAG 的编程连接的问题很可能是 ICA 客户端 13.1 的缺点(缺陷?)特定的客户端版本 - 因此无需专门准备 ICA 客户端对象即可在 CAG 环境中工作。
it is unlikely to have any other solutions here, so I consider my latest comment as an answer:
ICA Client 13.1 connects just fine (like client 10.200 did)
Thus issues with programmatic connections to CAG are likely to be the shortcomings (defects?) of particular client versions - so no specific preparation of ICA Client Object to work in CAG environment is necessary.