Este contenido no está disponible en el idioma seleccionado.

Chapter 4. Red Hat 3scale API Management 2.13


This document is intended for use with Red Hat 3scale API Management 2.13 On-premises.

4.1. New features

Red Hat 3scale API Management 2.13 provides the following new features:

  • Red Hat 3scale API Management deployed on OpenShift with FIPS (Federal Information Processing Standards) mode enabled is now supported (THREESCALE-5725).
  • Minor user interface improvements (THREESCALE-825, THREESCALE-8270).

4.2. Technology Preview features

Important

Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see https://access.redhat.com/support/offerings/techpreview/.

Red Hat 3scale API Management 2.13 provides the 3scale operator for application capabilities as a Technology Preview feature. The 3scale operator enables the use of custom resources to define 3scale tenants, APIs, application plans, limits, metrics, and other objects for use in a 3scale installation (THREESCALE-3486). See Using the 3scale operator to configure and provision 3scale.

3scale operator application capabilities have been improved in 3scale 2.13 with:

4.3. Resolved issues

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

Expand
Table 4.1. Resolved issues
Issue numberDescription

THREESCALE-8601

Algorithm parameter JWK "alg" check should be optional.

THREESCALE-8485

APIcast cannot retrieve latest version of proxy config

THREESCALE-8426

APIcast strips request path for proxied https requests

THREESCALE-8115

Autocomplete attribute for the credentials fields in the login page fixed

THREESCALE-8066

Default plan card disappears when searching for plans.

THREESCALE-7906

Too large request URIs make identifying errors in the APIcast logs difficult.

THREESCALE-7349

Nginx Filter policy UI - The boolean field is not False by default when unchecked.

THREESCALE-7327

The mapping rule search pagination is not displayed on the search results page.

THREESCALE-6405

Searches incorrectly return all records when searching by the name of the class.

4.4. Known issues

Known issues in Red Hat 3scale API Management 2.13:

Expand
Table 4.2. Known issues
Issue numberDescription

THREESCALE-8417

In 3scale, search does not work for products, backends, or accounts that are older than 24 hours

THREESCALE-7514

The NGINX Filters policy has no effect if you also add the Content Caching policy. The default behavior is that content caching is disabled. If you enable content caching, NGINX returns a 412 response code when it cannot validate a request header even if you specified that header when you added the NGINX Filters policy.

THREESCALE-8934

Upgrade with APIcast Operator from 2.12 to 2.13 fails.

For more information, refer to the workaround described in this knowledge article.

Issue resolved in 2.13.1

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.
Volver arriba
Red Hat logoGithubredditYoutubeTwitter

Aprender

Pruebe, compre y venda

Comunidades

Acerca de la documentación de Red Hat

Ayudamos a los usuarios de Red Hat a innovar y alcanzar sus objetivos con nuestros productos y servicios con contenido en el que pueden confiar. Explore nuestras recientes actualizaciones.

Hacer que el código abierto sea más inclusivo

Red Hat se compromete a reemplazar el lenguaje problemático en nuestro código, documentación y propiedades web. Para más detalles, consulte el Blog de Red Hat.

Acerca de Red Hat

Ofrecemos soluciones reforzadas que facilitan a las empresas trabajar en plataformas y entornos, desde el centro de datos central hasta el perímetro de la red.

Theme

© 2025 Red Hat