4.16.05.01 - Edge for Private Cloud release notes

On Thursday, July 21, 2016, we released a new version of Apigee Edge for Private Cloud.

Update procedure

This release includes the update.sh utility that you use to update your existing 4.16.05 installation to use the latest RPMs and support files. To use update.sh to update your existing 4.16.05 installation to the latest 4.16.05.01 version, see Update Apigee Edge 4.16.05.x to latest 4.16.05 release.

Bugs fixed

The following bugs are fixed in this release.

Issue ID Description Build number
EDGEUI-614

Improve Proxy from WSDL Generation

In the Build a Proxy wizard, when you create a SOAP API proxy as a pass-through proxy type, security options (API Key, OAuth 2.0, and CORS headers) are disabled in the Security wizard page.

edge-ui-4.16.05-0.0.3665
EDGEUI-627 The value of PLAY_SESSION for the Edge UI is not changing across different login sessions edge-ui-4.16.05-0.0.3665
PRC-791

Add ZooKeeper zk-tree.sh utiltiy

Include the ZooKeeper zk-tree.sh utiltiy, which you can use to debug and troubleshoot ZooKeeper issues. The utility is located at:

/<install_dir>/apigee/apigee-zookeeper/contrib/zk-tree.sh.

apigee-zookeeper-3.4.5-1.0.899
APIRT-2908

Support TLS 1.2 by default in a virtual host

Virtual hosts now support TLS 1.2.

edge-gateway-4.16.05-0.0.598
DEVRT-2634

"Error fetching webhooks" message appears in Edge UI whenusing Monetization

With Monetization enabled, the Edge UI displayed the message "Error fetching Webhooks" when you tried to perform actions on the Packages page. That error has been fixed.

edge-ui-4.16.05-0.0.3665
MGMT-2930
Data Masking not working in debug session
Trace data was not being masked correctly when running in debug mode.
edge-gateway-4.16.05-0.0.598
MGMT-3330

When using an External Authentication server, a single incorrect login locks the user out of the Edge UI

In previous releases when using an external authentication server, a single incorrect login attempt to the Edge UI locked out the user, even if the user was allowed multiple login attempts. That issue has now been fixed.

edge-gateway-4.16.05-0.0.598

edge-ui-4.16.01-0.0.3665

Known issues

This release has the following known issues.

Issue ID Description
APIRT-2978

Router fails to start Nginx or Router fails to start

If the Edge Router fails to start Nginx or fails to start at all, as shown in the /opt/apigee/var/log/edge-router/logs/system.log file, then delete all files in the /opt/nginx/conf.d directory, and restart the router:

> rm -f /opt/nginx/conf.d/*
> /opt/apigee/apigee-service/bin/apigee-service edge-router restart
APIRT-3364

Message Processor does DNS lookup on IPv4 and IPv6

If you have installed and enabled NSCD (Name Service Cache Daemon) you might notice that Message Processors make two DNS lookups: one for IPv4 and one for IPv6.

To disable the DNS lookup on IPv6:

  1. On every Message Processor node, edit /etc/nscd.conf.
  2. Set the following property:

    enable-cache hosts no
PRC-1118

Error when running "apigee-service apigee-postgresql pg-data-purge" command

If you run the "apigee-service apigee-postgresql pg-data-purge" command and see an error in the form:

ERROR: must be owner of relation

Edit /opt/apigee/apigee-postgresql-4.16.05-0.0.894/lib/actions/pg-data-purge and set the following property to 'apigee':

POSTGRES_USER=apigee

DOC-1687 Due to a known package dependency conflict, the Katello agent used in Satellite Server 6 will not install properly on Apigee Edge hosts running the Qpid daemon.