You're viewing **Apigee Edge** documentation.  
[Go to the
**Apigee X** documentation](http://cloud.google.com/apigee/docs). info

> [!NOTE]
> **Note:** Edge / Pivotal CF integration: [Edge
> integration with Pivotal Cloud Foundry](https://docs.apigee.com/api-platform/integrations/cloud-foundry/edge-integration-pivotal-cloud-foundry)
>
> Edge / Open source CF integration: [Cloud Foundry and Apigee Edge Integration](https://github.com/apigee/pivotal-cf-apigee)

## New features and enhancements

### Authentication with OAuth2
tokens

The service broker now supports authentication with OAuth2 tokens (recommended) or Basic
authentication. As described in "Creating an Edge API proxy," you can easily get an
OAuth2 token from your Edge instance and pass it with requests to bind a route service to an Edge
proxy.

### Apigee no
longer stores your org admin user ID and password

With this release's support for OAuth2, you no longer need to submit your Edge user ID
and password when creating an instance of the service broker. Instead, you can authenticate with
an OAuth token you retrieve separately from Edge.

### Fewer dependencies

With this release, external storage for route and binding configuration is no longer required,
simplifying deployment. Previously, the Apigee Edge service broker used Redis to store route and
binding configuration. The broker now requires that you pass configuration information with every
bind call. Unbinding no longer does any clean up; if you unbind, simply pass the configuration
information when you bind a proxy.

### Optional integration of Edge Microgateway with Cloud Foundry

You can optionally integrate Edge Microgateway with Cloud Foundry. You can do this through an
add-on that you include in Edge Microgateway. You can then push your Edge Microgateway instance
to Cloud Foundry, where it will be managed by Cloud Foundry.

For more information, see [readme content for
the add-on](https://github.com/apigee/pivotal-cf-apigee/tree/master/microgateway-addons).

### Automatic Edge
Microgateway configuration refresh

As Edge Microgateway is dynamically scaled in Cloud Foundry, configuration for new instances
automatically refreshed (there is no practical way to command some arbitrary number of instances
to reload their configs). Edge Microgateway reloads after there are new or changed proxies.

### Improved documentation

See the following links for documentation content:

- [Edge
  integration with Pivotal Cloud Foundry](https://docs.apigee.com/api-platform/integrations/cloud-foundry/edge-integration-pivotal-cloud-foundry) (overview)
- [Creating an Edge API proxy to manage client calls to your Cloud Foundry application](https://docs.apigee.com/api-platform/integrations/cloud-foundry/creating-edge-api-proxy-manage-client-calls-your-cloud-foundry-application) (using the service broker with Pivotal Cloud Foundry)
- [Apigee Edge
  Microgateway Add-ons for Cloud Foundry](https://github.com/apigee/pivotal-cf-apigee/tree/master/microgateway-addons) (running Edge Microgateway in Cloud Foundry)
- [Cloud
  Foundry Service Broker for Apigee](https://github.com/apigee/pivotal-cf-apigee/tree/master/apigee-cf-service-broker) (installing the service broker from source)