You integrate the Workspace ONE Access and Workspace ONE UEM services to enable devices enrolled in Workspace ONE UEM Mobile Device Management to use Workspace ONE Access single sign-on and identity management services.
UEM Integration Features to Configure in Workspace ONE Access
In the UEM integration page, you manage the Workspace ONE Access integration with the Workspace ONE UEM service.
| Option | Description |
|---|---|
| Workspace ONE UEM Configuration | You run the Getting Started wizard in the Workspace ONE UEM console to connect the Workspace ONE UEM service to the Workspace ONE Access service and establish a trusted relationship between the two services. The settings created in the Getting Started wizard are populated to the UEM Integrations page in the Workspace ONE Access console. To complete the configuration, you can enable Domain Mapping and verify that the App Catalog setting is correct. |
| Compliance Check | You enable compliance checking on the UEM Integration page and configure Device Compliance in the Integrations > Authentication Methods page to verify that managed devices adhere to Workspace ONE UEM compliance policies. When Device Compliance is configured, access policy rules can be configured to check the Workspace ONE UEM server for device compliance status when users sign in from their devices. See Enabling Compliance Checking for Workspace ONE UEM Managed Devices in Workspace ONE Access. |
| User Password Authentication through Workspace ONE UEM | Password Authentication with Workspace ONE UEM authenticates using AirWatch Cloud Connector through the Workspace ONE UEM service. When AirWatch Cloud Connector is used, you enable User Password Authentication through Workspace ONE UEM in the UEM Integration page and configure Password (with Workspace ONE UEM) in the Integrations > Authentication Methods page. You create access policies to apply to this authentication method. |
| User External Access Token Authentication through Workspace ONE UEM | When users receive a new Dell® Windows 10 device with out-of-box (OOBE) provisioning enabled in the Workspace ONE UEM Windows 10 Provisioning Service, you can enable User External Access Token Authentication through Workspace ONE UEM and configure Workspace ONE UEM External Access Token in Workspace ONE Access to manage Workspace ONE Intelligent Hub app logins. |
To configure Workspace ONE Access and Workspace ONE UEM service integration, see the Guide to Deploying VMware Workspace ONE UEM with Workspace ONE Access.
Example of UEM Integration Page after Trusted Relationship is Established
When you integrate Workspace ONE UEM and Workspace ONE Access, users from Workspace ONE UEM enrolled devices can log in to their Workspace ONE Intelligent Hub app to access their enabled applications securely without entering multiple passwords.
You run the Workspace ONE Getting Started wizard in the Workspace ONE UEM console to connect the Workspace ONE UEM service to the Workspace ONE Access service and establish a trusted relationship between the two services.
After you configure the settings in the Workspace ONE UEM console, the settings are automatically populated to the Workspace ONE Access console page.
The Fetch from Workspace ONE UEM is automatically enabled in the Catalog section to include apps from the Workspace ONE UEM catalog. The Workspace ONE Intelligent Hub app catalog displays web and virtual apps configured in the Workspace ONE Access console and native apps and web links configured in the Workspace ONE UEM console. The Device Service URL for new device enrollment with UEM is automatically configured.
When you integrate Workspace ONE Access and Workspace ONE UEM, any changes you make to the integration settings in one console must also be made in the other console. For example, if you update the REST API certificate in the Workspace ONE UEM console, you must upload the same certificate to the UEM Integration page in the Workspace ONE Access console.
