At this point you should have finished the three prior steps:
The next step involves setting the user accounts and tenants. By default, we have already created the default tenant at https://vcac-appliance-hostname.domain.name/shell-ui-app (in my case https://vcac-identity.kendrickcoleman.c0m/shell-ui-app) that can be accessed with the firstname.lastname@example.org SSO account.
vCAC has the ability to be a Single Tenant or Multi-Tenant application. A tenant is an organizational unit within a vCloud Automation Center deployment. A tenant can represent a business unit within an enterprise or a company that subscribes to cloud services from a service provider. Each tenant has a unique URL to the vCloud Automation Center console where the default has been specified above, while mutli-tenant resources will be given a URL such as https://vcac-appliance-hostname.domain.name/shell-ui-app/org/mycompany. The default tenant is the only tenant that supports native Active Directory authentication; all other tenants must use Active Directory over LDAP or OpenLDAP.
In a single tenant configuration, everything is handled at the default instance. This includes system wide configurations. Tenant administrators can manage users and groups, configure tenant-specific branding, notifications, business policies, and catalog offerings. The system administrator account is always email@example.com, while the tenant administrator must be a user in one of the tenant identity stores, such as firstname.lastname@example.org.
In a multi-tenant environment, the system administrator creates new tenants for each organization that uses the same vCloud Automation Center instance. Tenant users log in to the vCloud Automation Center console at a URL specific to their tenant. Since we are only going to be exploring a Single Tenant configuration, please read more about multi-tenancy at Comparison of Single-Tenant and Multi-Tenant Deployments in the official VMware documentation.
Add a comment