Skip to main content

VMware Cloud Director

Visualize VMware Cloud Director organizations, VDCs, VDC groups, edge gateways, networks, firewall rules, virtual machines, users, and roles, and monitor changes through queries and alerts.

Installation​

info

The integration authenticates against the VMware Cloud Director CloudAPI as a tenant-scoped user. System (provider/sysadmin) login is not currently supported, so the configured user only sees the organization it logs in to.

Configuration in VMware Cloud Director​

You will need a VMware Cloud Director user with read access to the resources you want to ingest (organizations, users, roles, VDCs, VDC groups, edge gateways, networks, firewall rules, and virtual machines).

Collect the following information for use when configuring the integration in JupiterOne:

  • The API host of your VMware Cloud Director instance, e.g. vcd.example.com.
  • The username of the tenant user the integration will sign in as. The value must not contain @ or : characters — VMware Cloud Director uses both as delimiters in the basic-auth credential it accepts at POST /cloudapi/1.0.0/sessions.
  • The password for that user.
  • The organization name the user belongs to. As with the username, the value must not contain @ or : characters.

The integration uses these credentials to obtain a bearer JWT from POST /cloudapi/1.0.0/sessions (returned via the X-VMWARE-VCLOUD-ACCESS-TOKEN response header) and re-mints the token automatically on 401 responses, so long collection runs survive the token's lifetime.

Configuration in JupiterOne​

To install the VMware Cloud Director integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select VMware Cloud Director. Click New Instance to begin configuring your integration.

Creating a VMware Cloud Director instance requires the following:

  • The Account Name used to identify the VMware Cloud Director account in JupiterOne. Ingested entities will have this value stored in tag.AccountName when the AccountName toggle is enabled.

  • Description to assist in identifying the integration instance, if desired.

  • Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as DISABLED and manually execute the integration.

  • The API Host, Username, Password, and Organization Name collected in the previous section.

Click Create once all values are provided to finalize the integration.

Next steps​

Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.