Skip to content

API Authentication

Overview¤

If you're interacting with an AUCyber VMware Cloud Director (VCD) environment beyond the web GUI, note that the authentication method changes with the AUCyber Portal at portal.aucyber.com.au.

Affected VMware tools and services include, but are not limited to:

What's changed?¤

The Portal logs you in to VCD using Single Sign-On (SSO), replacing the previous LDAP-based accounts.

Important: VCD does not support username + password authentication for SSO accounts, and you are no longer able to create local VCD users. Any new tool or integration that needs to authenticate to VCD must use a VCD API token.

If you already have a local VCD user, it will remain active and you can continue to use it to authenticate to the VCD API. Note that Broadcom has deprecated local users in VMware Cloud Director from version 10.4.1 onwards. Local users remain fully supported until the next major release of VMware Cloud Director, for which Broadcom has not yet published a date. See the "Deprecation Process for VMware Cloud Director Local Users for Production Use" notice in the VMware Cloud Director 10.6 Release Notes. We recommend that you move any existing integrations to a VCD API token now.

What to do next?¤

To continue accessing AUCyber VCD instances and using related tools (APIs, Terraform Provider, PowerCLI, etc.), create a VCD API token and use it to authenticate:

  1. Create a VCD API token from the Portal
  2. Follow Authenticating into VMware Cloud Director to exchange the token for a bearer token

Tool specific guidance is available for Terraform and PowerCLI.

Getting Support¤

Please refer to this guide for information on getting support in general at AUCyber.