You're viewing Apigee Edge documentation.
Go to the Apigee X documentation. info
On Thursday, March 26, 2015, we released a new cloud version of Apigee Edge.
New features and enhancements
Following are the new features and enhancements in this release.
Following are new features and enhancements in Edge Developer Services.
Swagger 2.0 support for SmartDocs
SmartDocs supports importing Swagger 2.0 specification documents and maintains backward compatibility with Swagger 1.2.
Following are new features and enhancements in Edge monetization.
Separate handling of Companies and Developers
Companies and developers are now handled separately, allowing for more flexibility in adding multiple companies to developers and multiple developers to companies. The management UI now provides separate windows for "Companies" and "Developers" (accessible from the "Publish" menu).
In monetization reports, companies remain a primary filter, though the filter label has changed from "Developers" to "Companies".
Following are new features and enhancements in Edge API Services.
New OAuthV2 fault variables
These new fault-related variables are set by the OAuthV2 policy:
- oauthV2.<policy-name>.failed - Set to true if the policy failed.
- oauthv2.<policy_name>.<fault_name> - The name of the fault. For example, invalid_request
- oauthv2.<policy_name>.<fault_cause> - The fault reason. For example: Token Expired
When creating a new product, you can now specify the product name in addition to the display name.
UI for removing users from an organization
On the Organization Users page in the UI, the Delete button was replaced with a Remove button. This is to help make it clear that when you remove a user from an organization, that user's Apigee account remains active.
Following are new features and enhancements in Edge Analytics Services.
Variables added to analytics
The following new variables are passed to Edge analytics, visible in the AX stage of the API proxy trace window.
- apigee.edge.execution.is_target_error - Lets you identify whether API errors are target-side errors (value "1") or non-target errors for unsuccessful HTTP responses (value "0"). The value is null for a successful HTTP response.
apigee.edge.execution.is_policy_error - Lets you identify if a policy failed
(value "1") or no policy failed in an unsuccessful HTTP response (value "0"). The value is
null for a successful HTTP response.
The following related variables provide details of the policy that failed first. The values are null if no policy failed.
- apigee.edge.execution.fault_policy_name - The name of the policy that failed.
- apigee.edge.execution.fault_flow_name - The name of the flow in the policy that failed (such as PreFlow, PostFlow, or a user-defined flow).
- apigee.edge.execution.fault_flow_state - The location where the policy was attached in the flow. Possible values: PROXY_REQ_FLOW, TARGET_REQ_FLOW, TARGET_RESP_FLOW, PROXY_RESP_FLOW.
The following bugs are fixed in this release.
|The UI throws an error when selecting a point in the Analytics tab of any list
|External XML Entity Injection - XXE in remote WSDL parsing using FTP servers
|UI Dashboard - Developer count limited to 10000
|When editing a product, turning off an environment in the UI does not save the change
|Need help explaining the WARN messages in system.log
|UI to support Authentication Response object for RBAC calls
|Support UI with Authentication Response object
|In API Proxy listings page, show last modified date as tooltip
|Place all AX date pickers to the left, as in proxy performance
|UI - Sorting only sorts currently displayed page
|Search for Consumer Key in "Developer Apps" does not workany more
|Details links on Traffic Composition report take you to same page
|Switching orgs with the dropdown does not work reliably
|Devices page shows unknown, other, others as different values
|Handle "(not set)" the same as we do with "na" values in analytics
|Remove timezone selector from analytics custom reports
|Proxy deployment failing when jsc resource files are stored at org scope
|Update Apache Commons Library for EmailValidation and other utils
|Make Dev Portal link in the management UI configurable
Fixes links from Edge UI (Developers page) to developer portals. If you have a developer portal that resides at a different location than the default link (Dev Portal button), contact Apigee Support to set the correct URL.
|UI login timeout doesn't work properly. User is never presented with a new authentication screen.
|On server start up self registration, register default type same as that of the profile
|Support authentication and security aspects of Swagger import in modeling
|Mask sensitive data in logs without affecting performance
In Edge message logging, the Authorization header value was visible. This issue has been fixed. The value is now masked.
|Better handling of removing users from orgs
The UI provides clearer labels about the impact of removing a user from an organization.
|UI is truncated when displayed through a projector in XGA resolution
|WADL import incorrectly adds body param called Content-Type
|Users with custom role cannot get report
The Custom Roles UI now surfaces permissions for company and developer apps.
|The Trace UI does not appear to be calculating policy elapsed time properly
|Trace error - while fetching object DebugSession not found
|API Product Name mangling
When creating or editing an API product, you can now see both the Display Name and internal Name of the API Product. While the Name remains fixed after you create an API Product, you can continue to modify the Display Name.
|Tax on Rate column needed in reports
A "Tax on Rate" (an amount) column is now available in reports. The "Tax/VAT" column has been changed to "Tax on Price", and the "Total Fees" column has been renamed to "Charged Rate".
|Tax applied to flat rate is not correct
|Prepaid Developer balance view is not populating topups
|Tax is applied to refund
|Runtime transactions are not rating when API resource is overridden through flow.resource.name
|Flat or Rate Card consider gross or net price if product enables in transaction recording policy
|Prorated recurring fee calculation is wrong
|E2E: ratelimit.Quota.failed is not set to true when quota exceeds
|API Proxy allows circular references
|Name of the policy having failure / raising fault
|Policy error count