Supporting Multiple TAS for VMs Instances

Page last updated:

Warning: VMware Tanzu Application Service for VMs (TAS for VMs) v2.9 is no longer supported because it has reached the End of General Support (EOGS) phase as defined by the Support Lifecycle Policy. To stay up to date with the latest software and security updates, upgrade to a supported version.

This topic describes registering a service broker with multiple VMware Tanzu Application Service for VMs (TAS for VMs) instances.

Overview

It may be necessary for the broker to know which TAS for VMs instance is making a given request. For example, when using Dashboard Single Sign-On, the broker is expected to interact with the authorization and token endpoints for a given TAS for VMs instance.

There are two strategies that can be used to discover which TAS for VMs instance is making a given request.

Routing and Authentication

The broker can use unique credentials, a unique URL, or both for each TAS for VMs instance. When registering the broker, you can configure different TAS for VMs instances to use different base URLs that include a unique ID. For example:

  • On TAS for VMs instance 1, the service broker is registered with the URL broker.example.com/123.

  • On TAS for VMs instance 2, the service broker is registered with the URL broker.example.com/456.

X-Api-Info-Location Header

All calls to the broker from TAS for VMs include an X-Api-Info-Location header containing the /v2/info URL for that instance. The /v2/info endpoint returns further information, including the location of that TAS for VMs instance’s UAA.

Support for this header was introduced in cf-release v212.