Before reviewing the example, it's recommended that you first read the How to Authenticate tutorial.
The example below shows the authentication experience when a user selects Cloud Orchestrator as their instance type.
How it works
The following steps and images are an example of how the connector works from design time (i.e., user inputs) to run time (i.e., sending the HTTP request).
- Select the Connection type that you want to connect to.
- The selection determines the Orchestrator API endpoint the connector sends requests to.
- Enter a Connection Name.
- This name is used to identify the connection within your application.
- A connector can have multiple connections to the same or different Orchestrator tenant. Each connection requires its own connection settings and may include the same or different credentials (i.e., Client Id and User Key). Adding multiple connections to the same tenant is useful if you plan to have multiple users that want to manage their own connections.
- Enter your Client Id and User Key.
- The User Key should be kept secret.
- Enter your Account Logical Name and Tenant Logical Name.
- For more information about how a user can locate their Client Id, User Key, Account Logical Name, and Tenant Logical Name see Getting the API Access Information in the Orchestrator API documentation.
- Klicken Sie auf Verbinden (Connect).
- The connector configures and sends a request with the entered inputs to
https://
. - The Orchestrator API responds with an
access_token
that you use for all subsequent API requests.
- The connector configures and sends a request with the entered inputs to

Vor ungefähr einem Jahr aktualisiert