Supporting Multiple CFAR Instances
Page last updated:
This topic describes registering a service broker with multiple Cloud Foundry Application Runtime (CFAR) instances.
It may be necessary for the broker to know which CFAR 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 CFAR instance.
There are two strategies that can be used to discover which CFAR instance is making a given request.
The broker can use unique credentials, a unique URL, or both for each CFAR instance. When registering the broker, you can configure different CFAR instances to use different base URLs that include a unique ID. For example:
On CFAR instance 1, the service broker is registered with the URL
On CFAR instance 2, the service broker is registered with the URL
All calls to the broker from CFAR 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 CFAR instance’s UAA.
Support for this header was introduced in cf-release v212.Create a pull request or raise an issue on the source for this page in GitHub