Omnissa One UEM
Connection Requirements
1 - Ip
The API server host of your Workspace ONE UEM environment. For a SaaS tenant this is the API host shown in the console, for example cn1831.awmdm.com. For an on-premises deployment it is the fully qualified domain name of your UEM server.
2 - Port
The port the UEM API listens on.
3 - Authentication type
Selects how the adapter authenticates. Use oauth2 for OAuth 2.0 client credentials, which is the method Omnissa documents for current tenants. Use basic only for older on-premises environments where an OAuth client cannot be created.
4 - OAuth token URL
The region specific token endpoint for your data centre, for example https://uat.uemauth.vmwservices.com/connect/token. The correct host for your region is listed in the Omnissa UEM documentation. Required when the authentication type is oauth2.
5 - Client id
The client identifier of the OAuth client created in the UEM console. Required when the authentication type is oauth2.
6 - Client secret
The client secret issued together with the client id. It is shown only once when the OAuth client is created. Required when the authentication type is oauth2.
In the UEM console navigate to Groups & Settings > Configurations > OAuth Client Management.
Select Add, give the client a descriptive name and choose the organization group the adapter should read.
Assign a role that grants read access to Devices and Enrollment Users.
Save the client and copy the Client ID and Client Secret before closing the dialog.
7 - Username
The UEM administrator account used for basic authentication. Required only when the authentication type is basic.
8 - Password
The password of the administrator account. Required only when the authentication type is basic.
9 - Tenant code
The REST API key of your organization group, sent as the aw-tenant-code header. You can find it under Groups & Settings > All Settings > System > Advanced > API > REST API, on the same screen as the REST API URL. It is required when the authentication type is basic, and is sent alongside the token when supplied with oauth2. Omnissa lists it among the values to collect for both flows, so provide it if your environment issues one.
10 - Fetch applications
When enabled, the adapter makes an additional request per device to collect the installed application list. This increases discovery duration considerably on large environments.
11 - Use serial as hostname
When enabled, the device serial number is used as the primary identifier instead of the host name. Enable this only when the host names reported by your environment are not reliable.
12 - Is secure
Determines whether requests are sent over HTTPS.
13 - Thread count
The number of parallel requests used while collecting application data. Accepts a value between 1 and 32.
14 - Sleep time
The delay in seconds inserted between parallel requests. Increase it if the UEM server throttles the adapter.
15 - Proxy
The proxy address to use when the UEM server is only reachable through a proxy.
16 - Timeout
The request timeout in seconds.
Last updated