You're viewing Apigee Edge documentation.
Go to the
Apigee X documentation. info
On Tuesday, March 4, 2014, we released a new cloud version of Apigee Edge.
New features and enhancements
- OAuth 2.0 - Reusing refresh tokens
Apigee Edge now provides an option (ReuseRefreshToken)
to enable OAuth 2.0 refresh tokens to be reused, rather than having new refresh tokens created
when a refresh_token grant request is issued.
Bugs fixed
| Topic |
Description |
| Policy changes |
Service callout URLs now support substitution of host name with flow variables. |
| API modeling |
-
Creating an API model success gives a 200 instead of a 201.
-
Model-driven docs now correctly include links to operations.
-
After WADL import, the user should be taken to the Operations page of the
“New API Proxy” wizard.
-
Importing a WADL which has query and body params causes the query params to be
displayed twice.
-
Optional query params are now correctly indicated on the Method page.
-
Methods with attachments are now correctly displayed.
-
Swagger import is now supported.
-
Multiple template model definitions are now supported.
|
| Error messages |
Several changes were made to address grammatically incorrect error messages. |
| API development |
-
An API called “resources” can now be correctly created, even with
scripts or other resources defined.
-
Debug sessions are now created correctly when using organization and environment
aliases.
|
| Roles and permissions |
- Resources at “/” can no longer be deleted.
- Organization-level role assignment and deletion is now handled correctly.
|
| Product stability and performance |
- Various performance enhancements have been included in this release.
- Edge on-premises now includes a “cluster ping” utility which
facilitates firewall issue detection.
|
