4.15.01.03 - Apigee Edge on-premises release notes

On Thursday, April 16, 2015, we released a patch for the on-premises version of Apigee Edge.

If you have questions, go to Apigee Customer Support.

For a list of all Apigee Edge release notes, see Apigee Release Notes.

New features

Following are new features in this release.

Server Name Indication (SNI) support

Edge supports the use of Server Name Indication southbound (from message processor to target endpoints) in on-premises deployments.

Java 1.7 is required.

With SNI, which is an extension of TLS/SSL, multiple HTTPS targets can be served off the same IP address and port without requiring all those targets to use the same certificate.

No Edge-specific configuration is required. If your environment is configured for southbound SNI (Edge cloud is by default), Edge supports it.

Edge automatically extracts the hostname from the request URL and adds it to the SSL handshake request. For example, if the target host is https://example.com/request/path, then Edge adds the server_name extension as shown below:

For more information on SNI, see http://en.wikipedia.org/wiki/Server_Name_Indication.

Disabling SNI

Apigee enabled SNI by default. You can disable this feature by setting the following property to false in /opt/apigee4/conf/apigee/message-processor/system.properties on the Message Processors:
jsse.enableSNIExtension=false

You must then restart the Message Processors using the command:

/opt/apigee4/bin/apigee-service message-processor restart