Which certificate is needed to configure Workspace ONE UEM Configuration with Workspace ONE Access?

Question

Options

• AWorkspace ONE UEM Device Services Certificate
• BWorkspace ONE UEM User Certificate
• CWorkspace ONE UEM Soap Certificate
• DWorkspace ONE UEM REST API Certificate

• A
  3% (1)
• B
  13% (5)
• C
  5% (2)
• D
  79% (30)

Explanation

Configuring the Workspace ONE UEM integration with Workspace ONE Access relies on REST API calls between the two platforms. The REST API Certificate (D) is what authenticates and secures those API-level communications - you export it from UEM and import it into Workspace ONE Access to establish trust for the integration.

Why the others are wrong:

• A (Device Services Certificate): This cert handles device-to-server enrollment and MDM communication - it's scoped to device interactions, not admin platform integration.
• B (User Certificate): User certificates are for authenticating end users (e.g., client certificate auth), not for service-to-service configuration between UEM and Access.
• C (SOAP Certificate): SOAP is a legacy protocol; Workspace ONE's modern integration layer uses REST, not SOAP endpoints, making this cert irrelevant for this configuration.

Memory tip: Think "REST = the way the two products talk to each other." Workspace ONE UEM and Access communicate via REST APIs, so naturally the REST API Certificate is the handshake that makes them trust each other.

No community discussion yet for this question.