When integrating a new application with your BetterCloud instance, the overall installation process is consistent. However, each integration is different, and may require varying levels and types of authentication. This article provides instructions for configuring and collecting all the information you need in order to add the Workspace ONE integration in BetterCloud.
BetterCloud requires the following authentication type when integrating with Workspace ONE:
- Username and Password (Basic HTTP Authentication)
You will also need to enter the following additional headers in order to successfully connect:
Username and Password
Enter the username and password of the admin account you will use to authenticate with Workspace ONE.
Base Host URL
The base host URL BetterCloud uses to structure our API calls can vary by Workspace ONE domain, so you will need to make sure you have the correct URL entered when adding the integration. To both retrieve this URL and enable API access, please follow the steps below.
From your Workspace ONE UEM console, navigate to “Groups & Settings” > “All Settings” in the left menu.
Select “Advanced” under the “System” settings.
Click on “API.”
Click on “REST API.”
Here you can view and configure the general settings for the Workspace ONE REST APIs. The REST API URL is the URL you will need to enter under base URL in your environment variables. Please copy only the domain name, as in the selected portion of the screenshot below.
Additionally, ensure that API access is enabled.
The tenant code in your Workspace ONE environment variables is equivalent to an API key, which you can generate from the same section where you retrieved your base URL. Select “Add” to create a new key.
You will need to provide a name for your service. Ensure that the account type is set to “Admin,” and copy your API key into the tenant code field in BetterCloud.
Once you have added your integration, you can update your username and password at any time under the integration’s basic information section. Your base URL and tenant code will be available as encrypted environment variables, and can be updated from there as well.