14.01.06.00 - Apigee Edge on-premises release notes
On Friday, April 4, 2014, we released a new 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 Edge Release Notes.
Following are the new features and enhancements in this release.
- Regenerate consumer keys in the UI
A new Regenerate Key button on the details page of a Developer App lets you regenerate a consumer key and consumer secret for a developer. Use this feature, for example, if an existing developer key is no longer secure.
|JMSReplyTo updated behavior||By default, Edge sends the response to the queue specified in the JMSReplyTo header. However, if you want the backend service to handle sending the response to the JMSReplyTo queue rather than Edge, add the
See JMS integration.
|WSDL import issues||
|Concurrent Rate Limit policy configuration||The Target Endpoint selector is now available only when adding a Concurrent Rate Limit policy to an API proxy. Target Endpoint does not apply to other policies.|
|Removing corrupted objects||In situations where a deployed bundle becomes corrupted, you can now forcibly delete the corrupted bundle using the
|Saving API proxies to an existing name||When you save an API proxy, name validation now disallows using the name of an existing proxy.|
|Different responses for XML and JSON||In some situations, different data was returned when an API response was in XML versus JSON. This issue has been fixed.|
|Custom report name validation||The Edge management UI now validates the names of custom reports to disallow the use of special characters.|
|No data in exported analytics reports||Analytics reports exported from the Edge management UI showed no data when the exported file name included special characters. The UI now validates the export file name to disallow the use of special characters.|
|Missing TPS metric in reports||Missing TPS metrics in analytics reports have been restored.|
|Cross-site scripting attacks||A vulnerability that allowed cross-site scripting attacks has been fixed.|
|Cassandra authentication||The Cassandra NoSQL data store now requires authentication for access.|
Help or comments?