Integrating Your Tool With Test Manager

概述

本主题中描述的授权方法提供有关如何在 Test Manager 与您的应用程序或其他合作伙伴应用程序之间建立服务到服务连接的信息。

先决条件

• 在 Orchestrator 中启用测试自动化。有关更多信息，请参阅“启用/禁用功能”。
• 在 Orchestrator 身份管理中生成安装令牌。您将需要通过命令行进行配置。要获取 Orchestrator 身份访问令牌，请参阅用于主机身份验证的外部提供程序。

授权代码

You can choose between two methods for provisioning an external OAuth client, based on specific use cases that are dependent on the versions used in your UiPath® product infrastructure:

• If you run both Test Manager and Orchestrator version 21.4 or above, you can use Provisioning through Identity Management.
• If you run Test Manager version 21.4 and Orchestrator version 20.10, or you want to enable cross-tenant access, you can use the Provisioning through Test Manager CLI.

通过身份管理配置

You can register your application in Identity Management, define the Test Manager scopes and establish a connection between the applications.

要配置和授权您的应用程序，您需要添加外部应用程序。

When you define the API scopes for the integration, select Test Manager as a Resource. For more information, see Scopes.

Provisioning through Test Manager CLI

Through the Test Manager CLI authorization, you can provision the client, assign scopes, and then establish a service-to-service connection between the applications.

To integrate and start using your application with Test Manager, you need to configure authorization: Provision client and scopes and then get a client ID and client secret.

配置授权

To establish a service-to-service connection between Test Manager and your application you will be using the Test Manager Provisioning Tool as the main CLI tool to get a client, provide access rights and scopes for your integration. You can find this tool packaged with each build as testmanager.exe in the default installation location, as follows:

C:\Program Files (x86)\UiPath\TestManager\Tools\TestManagerProvisioner。

Alternatively, you can find the executable in your custom installation folder. For a list of commands and options that are outside of the scope of your integration, see Test Manager Provisioning Tool Cheat Sheet.

以下部分列出了可用的命令行参数，包括选项和默认值，以便您配置访问权限和作用域，然后获取应用程序的客户端 ID 和客户端密码。

备注：

• 根据先决条件部分的要求，您将需要通过 Orchestrator 身份管理生成的安装令牌。
• You need to define Test Manager scopes.

命令	选项	描述
register third-party-s2sclient	-iu, --identityUrl (必填)	Identity Server 所在的绝对 URL。
	-iit, --identityInstallationToken <identityinstallationtoken> (必填)	用于在 Identity Server 中预配客户端的认证令牌。
	cscopes, --clientScopes <clientscopes> (必填)	显示创建客户端时要使用的客户端作用域。
	`-cid, --clientID <客户端 ID>`	显示创建客户端时要使用的客户端 ID。如果您不提供客户端 ID，系统会自动将其生成。
	-cname, --clientName <clientname>	显示创建客户端时要使用的客户端名称。如果您不提供客户端名称，则会自动生成此字段。
	-csecret, --clientSecret <clientsecret>	显示创建客户端时要使用的客户端密码。如果您不提供客户端密码，系统会自动将其生成
	-lang, --language <language>	指定错误消息的语言。
	-?, -h?, --help	显示帮助和用法信息。

Shell 脚本示例

在以下示例中，register third-party-s2sclient命令后跟 Orchestrator 身份 URL、身份安装令牌和 Test Manager 项目作用域。

testmanager.exe `
register third-party-s2sclient`
-iu "https://orchestratorURL/identity" `
-iit "e908741iofjikasjijfapuosf09210-012opjawdfsaodgfsadgu90029183i1jiratjapo" `
-cscopes "TM.Projects" "TM.Requirements.Read"
Client created successfully. Please note the data below right away. You will not be able to retrieve the secret afterwards.
ClientID: TestManager.ThirdPartyClient.36512487-1rfasdf-11451-321535
ClientName: TestManager.ThirdPartyClient.36512487-1rfasdf-11451-321535
ClientSecret: 43sdgj@efg145!fgdsg53125sfdg12a*gbj9