Creating more practical account credential possession and constructing upon the current API token with OAuth requirements, VMware Cloud Director (VCD) v10.4 introduces Service Accounts, as a substitute for consumer accounts, which permits standalone entry for automation and third-party functions/instruments (e.g. plugins) to VMware Cloud Director. Service Accounts have entry through API solely and no UI entry. Service accounts may be created both in system or tenant context, nevertheless, solely the system directors by default can create them. In case a corporation administrator/consumer wants the flexibility to create Service Accounts for his or her group, then view and handle rights may be granted to permit this.
Utilizing this functionality Cloud Director directors and tenant directors can successfully grant service accounts the proper to third social gathering functions and integrations, making it far simpler to handle who’s executing duties by not utilizing a consumer account for such processes. This implies there are not any higher controls over who does what and accountability that may be seen within the UI or API over actions.
