You're viewing Apigee Edge documentation.
Go to the
Apigee X documentation. info
On Wednesday, October 5, 2016, we began releasing a new version of Apigee Edge for Public Cloud. When your organization is updated, you'll see the new version number in the lower right of the Edge UI.
New features and updates
Following are the new features and updates in this release.
Developer app management goodness in the UI
Developer app management in the Edge UI has gotten more powerful with a number of enhancements:
- You can revoke and approve apps (in edit mode) in a new "App Status" field. In view mode, the field also displays the current app status. If an app is revoked, none of its API keys are valid for API calls. They keys themselves aren’t revoked and are available again for use if the developer is re-approved. The "Approved" label for API keys is displayed in strikethrough text while an app is in a revoked state.
- API key expiry dates are now shown on the Developer App Details page, and keys are organized by expiry dates in a "Credentials" section. For example, a key with no expiration is shown in one group with its associated API products, and a key that expires in 90 days is shown in another group with its associated products. You can’t change the expiration of an existing credential.
- With a new add Credential button in Developer App edit mode, you can generate API keys with
specific expiration times or dates (or no expiration). As (or after) you create a credential,
you can add API products to it.
This functionality replaces the "Regenerate Key" button on the Developer App Details page. That button has been removed.
These enhancements add features in the UI that were already available in the management API. (EDGEUI-104)
Activate/Deactivate app developer in the UI
You can change the status of an app developer between active and inactive in the Edge UI (Developer Details page, edit mode, Activate/Deactivate button). When a developer is inactive, none of her developer app API keys or OAuth tokens generated with those keys are valid in calls to API proxies. (EDGEUI-304)
OpenAPI Spec generation for SOAP proxies
When you create a "REST to SOAP to REST" proxy based on a WSDL, Edge automatically generates a
hosted OpenAPI Spec based on the proxy resources. You can access the spec at
http(s)://[edge_domain]/[proxy_base_path]/openapi.json. However, the conversion is
not always accurate, since not all the rules of an XML schema can be represented in an OpenAPI
Spec. (EDGEUI-718)
Edge-hosted WSDL for passthrough SOAP proxies
When you create a "Pass-Through SOAP" proxy based on a WSDL, Edge hosts the WSDL and creates a
flow in the proxy to let you access it. You can access the hosted WSDL at
http(s)://[edge_domain]/[proxy_base_path]?wsdl, which is the new service endpoint
URL for clients calling the SOAP service through the proxy. (EDGEUI-718)
Analytics "No Data" message includes delay interval
When the "No Data for Time Range" message appears in analytics reports, the message notes the delay interval between when API calls are made and when the data appears in analytics reports. (EDGEUI-682)
Bugs fixed
The following bugs are fixed in this release. This list is primarily for users checking to see if their support tickets have been fixed. It's not designed to provide detailed information for all users.
| Issue ID | Description |
|---|---|
| EDGEUI-697 | Reports page export button The Export button has been removed from the Custom Reports home page. Report export is available on each custom reports page. |