Skip to main content
Skip table of contents

Workspace ONE

Workspace ONE (formerly AirWatch) provides enterprise mobility management (EMM) software and standalone management systems for content, applications, and email.

Creating an API Key for Workspace ONE

Before configuring the Workspace ONE connector in Lucidum, you must first create an API Key. Lucidum will use the API key to access the Workspace ONE API.

  1. Go to the admin panel, click on Groups & Setting and then click on All Settings:

  2. After clicking, you will see a screen with new options to your left.
    Click System → Advanced → API → REST API. You will see this screen:

  3. Click add to create a new API key, add an indicative service name, set it to admin Account Type, copy the API key, and save it to a secure location (you will need it later on when configuring the connector). 

Configuring the Connector for Workspace ONE

To configure Lucidum to ingest data from Workspace ONE:

  1. Log in to Lucidum.

  2. In the left pane, click Connector.

  3. In the Connector page, click Add Connector.

  4. Scroll until you find the Connector you want to configure. Click Connect. The Settings page appears.

  5. In the Settings page, enter the following:

    •  URL (required): The URL of the VMWare Workspace ONE API. For example,

    • Username (required) - The credentials for a user account that has the permissions to fetch assets.

    • Password (required) - The credentials for a user account that has the permissions to fetch assets.

    • Client ID. Workspace ONE Client ID.

    • Client Secret. Workspace ONE Client secret.

    • Token URL. The URL for the access token.

    • API Key (required): API key for the REST API, created in the admin panel. 

    • Verify SSL. For future use.

  6. To test the configuration, click Test.

    • If the connector is configured correctly, Lucidum displays a list of services that are accessible with the connector.

    • If the connector is not configured correctly, Lucidum displays an error message. 

Supported Actions

  • Delete the registered devices identified by [Serialnumber]

  • Delete the enrollment user

  • Activate/Deactivate the enrollment user

  • Deploy a PowerShell script

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.