Release Notes

Red Hat 3scale API Management 2.4

For Use with Red Hat 3scale API Management 2.4

Red Hat Customer Content Services

Abstract

Release Notes for Red Hat 3scale API Management 2.4.

Chapter 1. Red Hat 3scale API Management 2.4 On-Premise Release Notes

1.1. Changes and New Features

1.1.1. Major Changes

1.1.2. Minor Changes

  • When a tenant is deleted from the Admin Portal, instead of being deleted directly, it is postponed for deletion. The developer will lose access to the provider’s APIs, but it will not actually be removed from the system until 15 days later.
  • APIcast API gateway:

  • Deployment. Changes in existing templates:

    • Unified shared configurations via ConfigMaps.
    • Moved existing sensitive information into Secrets.
    • Made all existing databases configurable externally.
  • Removed system-resque pod. Now system-sidekiq pod is handling everything that was handled by system-resque previously. (Content from issues.jboss.org is not included.JIRA #1695).

1.2. Resolved Issues

1.3. Documentation

1.4. Technology Preview Features

1.5. Known Issues

1.6. Deprecation and Replacement Notices

1.6.1. Deprecated in 3scale 2.4

  • End User Plans are deprecated in this release. Actual removal of this feature will be in March 2019. This feature will be replaced by the ability to define rate limits for end users using the APIcast policy for edge limiting. For more details, see Edge Limiting Policy
  • Latest transactions are deprecated in this release and will be removed in a future version. With the changes in 3scale user interface, references to the page with a live feed of the transactions reported from your APIs have been removed from the Admin Portal. As a temporary option to view the transactions, you can type the URL: [Your_admin_domain]/apiconfig/transactions.

1.6.2. Replaced in 3scale 2.4

  • Native OAuth 2.0 implementation (Authorization Code flow) for API traffic authentication has been removed in this release. This feature is replaced by the OpenID Connect integration with Red Hat Single Sign-On which includes support for multiple OAuth 2.0 flows. For more details, see OpenID Connect Integration.

Legal Notice

Copyright © 2019 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at Content from creativecommons.org is not included.http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.