Apigee deprecations, retirements, and CPS changes

This topic lists features that are being deprecated or have been retired. It also describes changes introduced by the Core Persistence Services (CPS) framework.

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.

For planning a move to Apigee Core Persistence Services, see CPS retirements and changes below.

Deprecations

Cloud or Private Cloud Announcement Date Item Description Retirement Date Retired in Private Cloud version
Cloud 10/10/2018

Deprecation of "Trireme"-based Node.js support

On the retirement date, Apigee will no longer support "Trireme"-based Node.js app deployment on Apigee Edge. Please migrate existing Node.js applications deployed on Apigee Edge to Hosted Targets. For additional assistance, see Migrating an existing Node.js proxy to a Hosted Targets proxy.

10/10/2019 N/A
Cloud 6/18/2018

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 on the Apigee blog.

7/23/2018 N/A
Cloud 6/15/2018

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.

  • PCI customers: June 29, 2018
  • Non-PCI customers: July 31, 2018

For more information, see TLS 1.0 and 1.1 retirement.

6/29/2018 (PCI customers)

7/31/2018 (Non-PCI customers)

N/A
Private Cloud 5/29/2018

Retirement of Monitoring Dashboard (Beta)

On May 29, 2018, Apigee retired support for the Monitoring Dashboard. For more information, see Monitoring Dashboard (Beta).

5/29/2018 4.18.05
Cloud 5/14/2018

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.

11/15/2018 ~4.19.01
Both 5/11/2018

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 on the Apigee blog and in Guidance for migrating from Apigee API BaaS.

6/30/2019 4.18.05
Cloud 4/16/2018 For the Get a Keystore or Truststore management API, the certs and keys properties will be removed from the response in a future release. A new aliases property is now available, which contains both the keys and the certs for each alias. TBD TBD
Cloud 4/3/2018

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:

N/A N/A
Cloud 3/6/2017 Edge classic persistence framework. See CPS retirements and changes below. 5/24/2018 ~ 4.18.05
Cloud 2/15/2017 Apigee secure store (vaults) TBD TBD

CPS retirements and changes

With the introduction of Core Persistence Services, a number of management APIs have changed. If your organization has not yet been moved to CPS, the following details are provided to help you understand the management API changes that will occur when you do move to CPS.

Feature Area Change with CPS
Key Value Map (KVM) identifier/name KVM names/identifiers are case sensitive. For example, if you create a KVM called FooBar, you'd reference that KVM in the Key Value Map Operations policy with the mapIdentifier attribute as mapIdentifier="FooBar".

Get KeyValueMap APIs:

In non-CPS organizations, the "Get KVM" API calls for different scopes (organization, environment, and proxy) returned a list of all KVMs, in addition to the keys and values in each KVM.

In CPS-enabled organizations, the Get KVM APIs return a list of only the first 100 KVMs at that scope. To the keys and values in each KVM, you must use the following APIs:

Get a list of keys in a KVM

Get the value for a specific key

Update KeyValueMap in an API proxy Not available in CPS. Replaced by Update a KeyValueMap entry in an API proxy (CPS).
Update KeyValueMap in an Environment Not available in CPS. Replaced by Update a KeyValueMap entry in an environment (CPS).
Update KeyValueMap in an Organization Not available in CPS. Replaced by Update a KeyValueMap entry in an organization (CPS).
Create API Product There is a custom attribute limit of 18.
Update API Product There is a custom attribute limit of 18.
Updates all API Product Attributes There is a custom attribute limit of 18.
Get Developer The response returns list of all apps for the developer. With CPS, the response includes only the first 100 apps. Pagination for a developer’s apps is not currently supported. To paginate a list of the developer's apps, use List App IDs in an Organization.
Create Developer There is a custom attribute limit of 18.
Update Developer There is a custom attribute limit of 18.
Delete Developer In CPS, associated resources such as apps are deleted asynchronously, which can take up to a few minutes.
Update all Developer Attributes There is a custom attribute limit of 18.
Create Developer App There is a custom attribute limit of 18.
Update Developer App There is a custom attribute limit of 18.
Delete Developer App In CPS, associated resources such as app keys or access tokens are deleted asynchronously, which can take up to a few minutes.
Get Count of API Resources for Developer App Not available in CPS. No replacement API.
Update all App Attributes There is a custom attribute limit of 18.
List App IDs in an Organization by Key Status CPS limits the number of entities returned to 1,000. The non-CPS limit is 10,000.
List App IDs in an App Family CPS limits the number of entities returned to 1,000. The non-CPS limit is 10,000.
List App IDs by App Type CPS limits the number of entities returned to 1,000. The non-CPS limit is 10,000.
List App IDs in an Organization CPS limits the number of entities returned to 1,000. The non-CPS limit is 10,000.
Create Company There is a custom attribute limit of 18.
Update Company There is a custom attribute limit of 18.
Create Company App There is a custom attribute limit of 18.
Update Company App There is a custom attribute limit of 18.
List Company App Families Not available in CPS. No replacement API.
Create Developer App Family Not available in CPS. No replacement API.
Update OAuth 2.0 Access Token There is a custom attribute limit of 18.
Update OAuth 1.0a Access Token There is a custom attribute limit of 18.
Update OAuth 1.0a Request Token There is a custom attribute limit of 18.
Get Count of OAuth 1.0 Access Tokens for a Developer App Not available in CPS. No replacement API.
Get a Count of OAuth 2.0 Access Tokens for a Developer App Not available in CPS. No replacement API.