- Getting Started
- Studio
- Orchestrator
- Testing robots
- Test Manager
- Licensing Test Manager
- Requirements
- Test Sets
- Executing Tests
- Test Results
- Documents
- Reports
- Bulk operations
- Troubleshooting
- Integrating Your Tool With Test Manager
- API Scopes
- CI/CD Integrations
Integrating Your Tool With Test Manager
The authorization methods described in this topic provide information on how to establish a service-to-service connection between Test Manager and your application, or other partner applications.
- Enable Test Automation in Orchestrator. For more information, see Enabling/Disabling Features.
- Generate an installation token in Orchestrator Identity Management. You will need this to provision through the command line. To get the Orchestrator Identity access token, see external providers for host authentication.
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.
To configure and authorize your application, you need to add an external application.
When you define the API scopes for the integration, select Test Manager as a Resource. For more information, see Scopes.
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.
The following section lists the available command-line parameters, including options and default values so you can provision access rights and scopes, and then get a client ID and client secret for your application.
- You will need the installation token generated through Orchestrator Identity Management, as requested in the prerequisites section.
- You need to define Test Manager scopes.
|
Command |
Option |
Description |
|---|---|---|
|
|
-iu,
--identityUrl (Required)
|
The absolute URL where Identity Server is located. |
-iit,
--identityInstallationToken
<identityinstallationtoken>
(Required)
|
The authentication token for provisioning clients in Identity Server. | |
cscopes,
--clientScopes <clientscopes>
(Required)
|
Show client scopes to be used when creating the client. | |
|
`-cid, --clientID <clientid>` |
Show the client ID to be used when creating the client. This is automatically generated if you do not provide a client ID. | |
|
|
Show the client name to be used when creating the client. This is automatically generated if you do not provide a client name. | |
|
|
Show the client secret to be used when creating the client. This is automatically generated if you do not provide a client secret | |
|
|
Specify the language of the error messages. | |
|
|
Show help and usage information. |
register
third-party-s2sclient command is followed
by the Orchestrator identity URL, identity
installation token and Test Manager project
scopes.
testmanager.exe <code>
register third-party-s2sclient</code>
-iu "https://orchestratorURL/identity" <code>
-iit "e908741iofjikasjijfapuosf09210-012opjawdfsaodgfsadgu90029183i1jiratjapo" </code>
-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*gbj9testmanager.exe <code>
register third-party-s2sclient</code>
-iu "https://orchestratorURL/identity" <code>
-iit "e908741iofjikasjijfapuosf09210-012opjawdfsaodgfsadgu90029183i1jiratjapo" </code>
-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
