CredHub Service Broker
The CredHub Service Broker allows apps running on VMware Tanzu Application Service for VMs (TAS for VMs) to access secure credentials in CredHub.
Apps can use these credentials to authenticate with services not on TAS for VMs, including services running on Ops Manager such as Spring Cloud Services and services external to Ops Manager.
The CredHub Service Broker uses secure binding credentials to prevent credential exposure in the app environment.
The CredHub Service Broker registers a service broker with TAS for VMs and exposes its service plans on the Marketplace. Developers can then create service instances using Apps Manager or the Cloud Foundry Command Line Interface (cf CLI) and bind them to their apps.
Creating a CredHub Service Broker instance and binding it to an app creates a credential in CredHub and provides the reference to that credential in the app environment. This allows developers to deploy apps that can securely access credentials for services that are not running on TAS for VMs.
The key feature of CredHub Service Broker is secure access to service credentials for services that are not running on TAS for VMs.
The following table provides version and version-support information about CredHub Service Broker.
|Release date||March 16, 2021|
|Software component version||v1.5.0|
|Compatible Ops Manager versions||2.7, 2.9, and 2.10|
|Compatible TAS for VMs versions||2.7, 2.9, 2.10, and 2.11|
|IaaS support||AWS, Azure, GCP, OpenStack, and vSphere|
CredHub Service Broker has the following requirement:
- Secure binding credentials enabled in runtime CredHub
To enable secure binding credentials in runtime CredHub, see Securing Services Instance Credentials with Runtime CredHub (Beta).