Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Release Notes for Red Hat 3scale API Management 2.14 On-premises

Red Hat 3scale API Management 2.14

Document intended for use with Red Hat 3scale API Management 2.14

Red Hat Customer Content Services

Abstract

This document informs users about the latest and Technology Preview features, as well as resolved issues, associated documentation, and known issues in Red Hat 3scale API Management 2.14

Preface
Copy link

This document is intended for use with Red Hat 3scale API Management 2.14 and related patch releases.

Providing feedback on Red Hat documentation
Copy link

We appreciate your feedback on our documentation.

To propose improvements, open a Jira issue and describe your suggested changes. Provide as much detail as possible to enable us to address your request quickly.

Prerequisite

  • You have a Red Hat Customer Portal account. This account enables you to log in to the Red Hat Jira Software instance. If you do not have an account, you will be prompted to create one.

Procedure

  1. Click the following Create issue.
  2. In the Summary text box, enter a brief description of the issue.

  3. In the Description text box, provide the following information:

    • The URL of the page where you found the issue.
    • A detailed description of the issue.
      You can leave the information in any other fields at their default values.
  4. Click Create to submit the Jira issue to the documentation team.

Thank you for taking the time to provide feedback.

1.1. Resolved issues and enhancements
Copy link

Red Hat 3scale API Management 2.14.3 provides the following improvements and fixes:

  • Addressed security vulnerabilities, including the fix for CVE-2024-10295.
  • Applied minor stability improvements.

2.1. New features
Copy link

Red Hat 3scale API Management 2.14.2 provides the following new features and enhancements:

  • Added compatibility for OpenShift version 4.16.
  • Applied CVE patches to the base images for improved security.

3.1. New features
Copy link

Red Hat 3scale API Management 2.14.1 provides the following new feature:

  • Added compatibility for Red Hat OpenShift version 4.15.

3.2. Resolved issues
Copy link

Red Hat 3scale API Management 2.14.1 resolves the following issue:

  • Resolved Token Introspection policy compatibility issue with Red Hat Single Sign-On 7.5 or later.

Chapter 4. Red Hat 3scale API Management 2.14.0
Copy link

4.1. New features
Copy link

Red Hat 3scale API Management 2.14 provides the following new features and enhancements:

  • Content Management System API (THREESCALE-7891):

    • Introducing the new Content Management System API (CMS API) that allows programmatic control and provision of the Developer Portal content.

  • 3scale API Management Operator for Application Capabilities (THREESCALE-3486):

  • STS authentication for Amazon S3 (THREESCALE-7132):

    • Added support for AWS Security Token Service (STS) authentication in S3 buckets used by 3scale.

  • API gateway (APIcast) enhancements:

    • Added support for OpenTelemetry distributed tracing in APIcast (THREESCALE-7735)
    • Loading configuration via /admin/api/account/proxy_configs is now supported (THREESCALE-8508)
    • Ability to set the APICAST_SERVICE_CACHE_SIZE for improved caching (THREESCALE-8749)

  • 3scale Operator Enhancements:

    • Definition of pod priorities for components via APIManager CR (THREESCALE-8997)
    • Setting of zone topology spread constraints for components via APIManager CR (THREESCALE-8998)
    • Addition of labels to components via APIManager CR (THREESCALE-8999)
    • Support for OAuth2/OIDC in the OpenAPI CRD (THREESCALE-9573)

  • Toolbox CLI Enhancements:

    • Support for OpenAPI specifications with multiple flows in OAuth2 security schemes (THREESCALE-9768)

  • Security, performance, and other general improvements:

    • Improved JSON spec invalid error feedback in the Admin Portal UI (THREESCALE-8034)
    • Hits metrics display as integers for easier interpretation (THREESCALE-8036)
    • Added support for policy chains with sizes greater than 65,535 bytes (THREESCALE-8377)
    • Improved integration with Oracle databases (THREESCALE-1175)
    • Use of secretKeyRef enabled for APIcast policies configurations (THREESCALE-8002)
    • Upgrade of 3scale APIs and online documentation to OpenAPI version 3 (THREESCALE-3927)
    • Allowed disabling Redis client ID for Sidekiq connection (THREESCALE-9210)
    • Improved security in the password update form: current password is now required. (THREESCALE-6648). For more information, see this article.
    • Added primary keys to all tables for Group Replication compatibility in MySQL (THREESCALE-9655)
    • Improved security with keys and access tokens masked in system logs (THREESCALE-5442)
    • Audition of new objects included in the 3scale audit logs (THREESCALE-6853)
    • Added ability to fetch whether Active Docs are published or not (THREESCALE-7403)

4.2. Resolved issues
Copy link

Red Hat 3scale API Management 2.14 resolves the following issues:

Expand
Table 4.1. Resolved issues
Issue numberDescription

THREESCALE-6835

Zync requires zync-que redeploy for routes to be created

THREESCALE-7315

Failing to deploy APIManager via the operator with external Oracle database - service name and PDB mismatch

THREESCALE-7431

Developer portal’s spam protection 'Suspicious only' doesn’t work correctly

THREESCALE-7941

Review warning displayed in apicast logs about variables_hash_max_size & variables_hash_bucket_size

THREESCALE-7942

Apicast logs shows permission denied in a tmp file

THREESCALE-7945

APICAST_PATH_ROUTING=true causes 404 when it should use the stale config object

THREESCALE-8131

Fix New Product form

THREESCALE-8373

APIcast does not load all pages of services or proxy configs

THREESCALE-8417

Search in on prem doesn’t work for records older than 24 hours

THREESCALE-8562

Products and backend can’t be found by searching for system name

THREESCALE-8572

3scale Backend Operator capability does not allow creating more than 500 methods

THREESCALE-8707

Toolbox command "application apply" returning error after API Credentials regenerated through the Portal

THREESCALE-8719

The default metric should be a Product’s metric

THREESCALE-9003

Loss of APICast configuration

THREESCALE-9010

When downloading the Active Doc 3scale adds "schemes":["http"]" at the end

THREESCALE-9193

APIcast fails to connect to upstreams that require TLS v1.3

THREESCALE-9476

3scale Backend Operator capability does not allow creating more than 500 Backends

THREESCALE-9570

"Service plan" created in another "Product" is displayed in the service plan list

THREESCALE-9626

ActiveDocs shows Error when a response body is blank

4.3. Known issues
Copy link

Known issues in Red Hat 3scale API Management 2.14:

Expand
Table 4.2. Known issues
Issue numberDescription

THREESCALE-7514

Nginx filter policy is not working as expected when using content-caching

THREESCALE-10602

Some migrations from 2.13 to 2.14 fail due to a bug. Follow the instructions in this solution from the Red Hat Customer Portal to avoid a potential upgrade failure.

Important

  • Usernames in 3scale must be 40 characters or fewer. When a username has more than 40 characters, 3scale usually truncates it. Consider this when you do any of the following:

    • Create a developer account.
    • Create a provider account as the master.
    • Add a user to a provider account as the provider or as the master.
    • Add a user to a developer account in the Developer Portal or in the Admin Portal.
  • Usernames must be 40 characters or fewer when using Red Hat Single Sign-On to authenticate access to the Admin Portal or Developer Portal.

Chapter 5. Documentation
Copy link

Supported configurations

Security updates

Erratas

Upgrade guides

Legal Notice
Copy link

Copyright © 2025 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 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.
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2026 Red HatBack to top