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 Copiar enlaceEnlace copiado en el portapapeles!
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 Copiar enlaceEnlace copiado en el portapapeles!
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:
-
Ability to promote
Product
configurations to Staging and Production APIcast (THREESCALE-7135) -
Declarative deletion of
DeveloperUser
(THREESCALE-7055) andDeveloperAccount
(THREESCALE-7052) custom resources.
4.3. Resolved issues Copiar enlaceEnlace copiado en el portapapeles!
Red Hat 3scale API Management 2.13 resolves the following issues:
Issue number | Description |
---|---|
Algorithm parameter JWK "alg" check should be optional. | |
APIcast cannot retrieve latest version of proxy config | |
APIcast strips request path for proxied https requests | |
Autocomplete attribute for the credentials fields in the login page fixed | |
Default plan card disappears when searching for plans. | |
Too large request URIs make identifying errors in the APIcast logs difficult. | |
Nginx Filter policy UI - The boolean field is not | |
The mapping rule search pagination is not displayed on the search results page. | |
Searches incorrectly return all records when searching by the name of the class. |
4.4. Known issues Copiar enlaceEnlace copiado en el portapapeles!
Known issues in Red Hat 3scale API Management 2.13:
Issue number | Description |
---|---|
In 3scale, search does not work for products, backends, or accounts that are older than 24 hours | |
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 | |
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 |
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.