You're viewing Apigee Edge documentation.
View Apigee X documentation.
This topic lists features that are being deprecated or have been retired.
Deprecations and retirements
The following Apigee Products, Services, and features are subject to the Apigee deprecation policy.
- Deprecated - The feature is still in the product but will be removed at a future date. Use alternative functionality, either described here in or in the relevant documentation.
- Retired - The feature is no longer in the product.
- The '~' symbol means estimated.
For more information about deprecations and retirements in Edge for Private Cloud, see Apigee deprecation policy.
|Cloud or Private Cloud||Announcement Date||Item Description||Deprecation Date||Deprecated in Private Cloud version|
Support for the
Apigee recommends that Private Cloud customers submit API traffic statistics manually, as described in Submitting API traffic statistics to Apigee.
Since 2013, Apigee has supported the use of Node.js proxies within Apigee Edge through the use of Trireme, which enables you to run your Node.js code within Apigee Edge for Private Cloud and expose it as an API.
Apigee recommends Private Cloud customers take the following steps:
|Public and Private Cloud||7/15/2020||
Support for OAuth V1 features.
Since IETF RFC 6749 has become the standard that replaced OAuth 1.0a, the maintainers of the OAuth v1.0a standard recommend that users switch to OAuth v2.0.
Deprecated policies include:
For improved security, Apigee recommends that Private Cloud customers migrate to using the OAuth v2 policies as soon as possible.
|Public and Private Cloud||7/15/2020||
Support for the Concurrent Rate Limit feature
The Concurrent Rate Limit policy was designed to be used with slow backends, however, the architecture used by it affected the performance of the APIs.
Since the Concurrent Rate Limit's announcement, Apigee has added newer capabilities such as chaining proxies together and shared flows. If you are experiencing slower performance with Concurrent Rate Limit policy, you can try using Spike Arrest instead.
You can read more details in our usage notes page.
Using such features along with policy, will allow you to protect slow/sluggish backends without impacting the performance of the APIs.
Migrate proxies using the Concurrent Rate Limit policy to the Quota policy and/or the Spike Arrest policies.
|Public and Private Cloud||7/15/2020||
Support for Istio by integrating with Istio Mixer
In March this year, the Istio community announced deprecation for Istio Mixer. The Istio Mixer component is critical for the functioning of the Apigee adapter for Istio, which is why we redesigned the Istio adapter to use native Envoy filters (see envoy filter and HTTP filters) to integrate with Apigee.
Apigee recommends that you migrate to Apigee adapter for Envoy as soon as possible.
Support for the Teams early access feature
The early access program for the Teams feature in Apigee has been canceled, and the Teams feature will be removed from Private Cloud.
If you are using Teams, Apigee recommends replacing the team entities and the permissions associated with those teams with custom roles. The roles can be granted to the same set of users that comprised the team to replicate the desired team structure.
Deprecation of sponsored hosting for Drupal portals
On the retirement date, Apigee will no longer provide sponsored hosting of Drupal-based developer portals. Customers wishing to continue using Drupal must assume their hosting responsibilities, see the Drupal 7 Transition FAQ.
Deprecation of monetization variance reports
On the retirement date, Apigee will no longer support monetization variance reports on Apigee Edge.
Deprecation of Personal space
On the retirement date, Apigee will no longer support Personal space on Apigee Edge. Copy your OpenAPI Specifications from your personal space to one of your other organizations.
Retirement of Monitoring Dashboard (Beta)
On May 29, 2018, Apigee retired support for the Monitoring Dashboard. For more information, see Monitoring Dashboard (Beta).
Deprecation of OAuth 1.0a
On the retirement date, Apigee will no longer support OAuth 1.0a. Please migrate any OAuth 1.0a usage in your API proxies to OAuth 2.0, and extend your OAuth 2.0 usage with signature verification (for message-level integrity checks) according to your needs.
Affected OAuth 1.0a policies include the OAuth v1.0a policy, Get OAuth V1 Info policy, and Delete OAuth V1 Info policy. Edge includes corresponding OAuth 2.0 policies.
Get a Keystore or Truststore management API, the
Update TLS configuration for a virtual host API
The Update TLS configuration for a virtual host API lets Edge for the Cloud customers update the TLS configuration properties for a virtual host.
Cloud customers can now create and update a virtual host, not just modify the TLS properties of the virtual host. Therefore, this API has been deprecated. Cloud customers can now use the following APIs with virtual hosts:
|Cloud||3/6/2017||Edge classic persistence framework.||5/24/2018||~ 4.18.05|
|Cloud||2/15/2017||Apigee secure store (vaults)||TBD||TBD|
|Cloud or Private Cloud||Announcement Date||Item Description||Retirement Date||Retired in Private Cloud version|
Apigee service broker for Pivotal Cloud Foundry EOL
Apigee service broker for Pivotal Cloud Foundry (PCF) will reach End of Life (EOL) on the retirement date shown here.
If you are currently using the service broker, you need to take the following actions before the retirement date:
Edge Installer for Pivotal Cloud Foundry EOL
The Apigee Edge Installer for PCF reached End of Life (EOL) on the retirement date shown here. For more information, see this community post.
Deprecation of "Trireme"-based Node.js support
As of the retirement date, existing Trireme is deprecated and will be retired on the date indicated. Please migrate existing Node.js applications deployed on Apigee Edge to Hosted Targets. For assistance, see Migrating an existing Node.js proxy to a Hosted Targets proxy.
For more information, see Trireme-based Node.js End of Life.
|10/10/2019||Until otherwise noted, the Trireme retirement will not affect usage of Trireme on Edge for Private Cloud installations.|
Apigee announces the deprecation of the Apigee Edge API Backend-as-a-Service (API BaaS) feature.
The API BaaS end of life (EOL) will be June 30, 2019. Apigee will continue to operate and support API BaaS until June 30, 2019, subject to the terms of our deprecation policy. Read more in this blog post, in the Deprecation and End of Life announcement, and in Guidance for migrating from Apigee API BaaS.
Note that the API BaaS Android push notifications functionality is reliant on Google Cloud Messaging (GCM), which will reach end of life on April 11, 2019. Please be advised that we will not upgrade the Apigee API BaaS solution to use the new Google Firebase Cloud Messaging (FCM) system, as this would require customers to migrate to this new messaging system while also planning to migrate off Apigee API BaaS altogether before June 30, 2019.
We recommend that Android push notification customers start their planning to migrate off of Apigee API BaaS for this functionality before April 11, 2019.
Retirement of monetization billing document generation
Apigee no longer supports the generation of billing documents from Apigee Edge Monetization.
The specific tasks that are retired and no longer supported for use with monetization include:
Retirement of BaaS Eval Orgs
On June 18, 2018, BaaS Eval orgs will no longer be accessible. This is being done as part of the BaaS EOL process, which you can read more about in this blog post and in the Deprecation and End of Life announcement.
Retirement of TLS 1.0 and 1.1 - Extension
Apigee will retire support for TLS versions 1.0 and 1.1 in the public cloud on the following dates.
For more information, see TLS 1.0 and 1.1 retirement.
November 9, 2018
Apigee Test End of Life
Apigee Test has been an Apigee labs project for some time. It provides the ability to synthetically monitor, check and notify the availability of you API endpoints. Apigee has decided to discontinue this service and will be decommissioning the Apigee Test site 45 days from the date of this notice.
Stackdriver’s black-box monitoring system, Uptime Checks, provides basic functionality of Apigee Test. Please consider utilizing its services if it works for your use cases. You can also use the in-app “Send Feedback” link to submit feature requests for your use case(s) to that Google product team.
|Cloud||11/21/2017||When you revoke an OAuth access token (or access tokens associated with a specific user), those actions will no longer be tracked for audit and will not appear in Audit management API calls.||~ April 2018||~ 4.18.09|
Apigee announces that it is discontinuing the use of Dedicated Instances for HIPAA compliance pack customers in AWS.
Expand to read more.
Apigee is discontinuing the use of Dedicated Instances (DIs) for HIPAA compliance pack customers.
Apigee Edge with HIPAA compliance pack has been using Amazon Web Services (AWS) DIs since its inception. The concept of DIs is that the hardware in AWS cloud is dedicated for use only by Apigee (but not to individual Apigee customers), and Apigee can launch multiple virtual machines on this hardware.
The use of DIs for HIPAA compliance pack customers was required by the Business Associate Agreement (BAA) in place between Apigee and AWS. AWS recently announced that DIs are no longer required in order to have a BAA in place between AWS and its customers. The use of DIs has never been required by the HIPAA regulations or by Apigee’s third-party auditors who review and attest to our compliance with HIPAA.
The concept of DIs is logical in a virtual machine environment, but does not lend itself well to a container-based platform (for example, Google Cloud Platform and Kubernetes). Because Apigee is a multi-cloud service, use of DIs in AWS does not integrate well into our service management processes.
The use of DIs in AWS has been unique in our management of the Apigee multi-cloud platform, and our experience shows that DIs have a higher rate of failure than standard instances. This experience has been reported publicly by other AWS DI users as well.
This change allows Apigee to provide a more consistent experience for Apigee customers.
|Cloud||RETIRED||Apigee Insights||October 2017||N/A|
|Cloud||2/15/2017||Paths in proxy Performance tab and Business Transactions dashboard||~ 2/15/2018||~ 4.18.05|
|The following retirements occurred before the Apigee deprecation policy.|
|Cloud||RETIRED||Apigee Console To-Go||12/31/2016|
|Cloud||RETIRED||API BaaS version 1 (moving to API BaaS 2)||12/19/2016|
|Cloud||RETIRED||Monetization Limits feature||10/1/2016|
|Cloud||RETIRED||API BaaS Mobile App Performance Monitoring||7/8/2016|
|Cloud||RETIRED||Monetization Setting limits and sending limit notifications||6/27/2016|
|Cloud||RETIRED||Hidden modules in Developer Portal: devconnect_content_admin, devconnect_docgen, devconnect_download, devconnect_multiorg, devportal_updates, devconnect_partner||6/22/16|
|Cloud||RETIRED||Node Export and Rubik modules in Developer Portal||4/11/2016|
|Cloud||RETIRED||Classic proxy editor||4/20/2016|
|Cloud||RETIRED||Display Suite module in Developer Portal||3/31/2016|
|Cloud||RETIRED||Edge legacy login||3/14/2016|
|Cloud||RETIRED||Various contrib modules in Developer Portal||3/7/2016|
|Cloud||RETIRED||async attribute on policy configurations||2/25/2016|
|Cloud||RETIRED||Management API: chargePerUsage attribute on updating monetization prepaid balance||1/26/2016|
|Cloud||RETIRED||Management API: Update a KVM (proxy, env, org)||When org is updated to CPS|
|Cloud||RETIRED||Management API: Get Keys, Apps, Developers, or Companies for an API Product||When org is updated to CPS|
|Cloud||RETIRED||Management API: List Company App Families||When org is updated to CPS|
|Cloud||RETIRED||Management API: Create Developer App Family||When org is updated to CPS|
|Private Cloud||RETIRED||QPID queue check API in Private Cloud||12/24/2015|
|Cloud||RETIRED||Custom Reports dashboard||10/1/2015|
|Cloud||RETIRED||X-Forwarded-For header by default||10/1/2015|
|Private Cloud||RETIRED||hash.oauth.tokens.enabled property in keymanagement.properties in Private Cloud||9/8/2015|
|Cloud||RETIRED||ProxyEndpoint properties: allow.http10, allow.http11, allow.http.method.*, allow.POST.without.content.length, allow.PUT.without.content.length||8/18/2015|
|Cloud||RETIRED||"Maximum Elements in Memory" property on environment cache resources||7/23/2015|
|Cloud||RETIRED||Aggregation Basis in Monetization||5/19/2015|
|Cloud||RETIRED||devconnect_multiorg module in Developer Portal||4/23/2015|
|Cloud||RETIRED||oauth-login-app GitHub sample||1/29/2015|
|Cloud||RETIRED||devconnect_docgen module in Developer Portal||11/13/2014|
|Cloud||RETIRED||API BaaS Assets||5/2/2014|
|Cloud||RETIRED||devconnect_apigee, devconnect_validate and devconnect_faq_ext modules in Developer Portal||1/29/2014|
|Cloud||RETIRED||WYSIWYG module in Developer Portal||7/25/2013|
|Cloud||RETIRED||API BaaS Filters|