订阅

概述

Orchestrator 的差异

UiPath Orchestrator 在各个部署选项中的功能大致相同,但有一些值得注意的例外情况,具体情况如此页面所述。
此页面上的信息涉及 Orchestrator 的以下部署选项:

  • On-premises deployment options:
    • 独立版 Orchestrator(内部部署,最新版本)
    • Orchestrator service in UiPath Automation Suite (on-premises platform, latest version)
  • Cloud deployment: Orchestrator service in UiPath Automation CloudTM

此页面会定期更新,以反映部署选项之间的差异,因此请定期查看此页面。

 

功能行为上的差异

On-premises behavior

Cloud behavior

API Authentication

On-premises Orchestrator can use:
basic authentication
the OAuth flow (2021.4 and later)

Automation Cloud, and therefore Orchestrator as well, can use two mechanisms:
tokens instead of basic authentication. More...
the OAuth flow

Libraries Feeds

For on-premises Orchestrator, you can publish libraries both at host and tenant level feeds

In Automation Cloud you can publish libraries only at tenant level. To share libraries between tenants, you can use a custom feed.

Password Complexity Settings

As an administrator of an on-premises Orchestrator, you can manage the password complexity for your host or organization.

By default, when users sign up for Automation Cloud and create their account, the password they set must meet specific requirements, which cannot be modified.
You can choose to change your Authentication Settings to use the Azure Active Directory integration, which allows you to configure password requirements.

约一个月前更新


Orchestrator 的差异


建议的编辑仅限用于 API 参考页面

您只能建议对 Markdown 正文内容进行编辑,而不能建议对 API 规范进行编辑。