For Red Hat Managed Integration 1
These release notes list the components of Red Hat Managed Integration 1.7, as well as known and fixed issues in this release.
When a Managed Integration patch or upgrade is available, you are notified and prompted to create an upgrade schedule. When prompted, see these Release Notes for details regarding changes to your cluster.
Chapter 1. Versions of Components
Red Hat Managed Integration 1.7 includes the following software versions:
Chapter 2. Fixed Issues
The following issue is resolved in Red Hat Managed Integration 1.7.1:
In previous versions of Red Hat Managed Integration, Red Hat AMQ Online console returned the message
500 Internal Error, Internal Errorand users were unable to log in. This error and inability to access the console occurred because a custom certificate used by the console created a trust issue between the
The following issue is resolved in Red Hat Managed Integration 1.7.0:
- The address space messaging endpoint in Managed Integration supported TLS 1.0 and TLS 1.1, which are weak cipher suites. As of this release, only TLS 1.2 is supported.
Chapter 3. Known issues
This section lists known issues with Red Hat Managed Integration 1.7:
- In the Managing and protecting APIs using API management Solution Pattern, users must have administrator privileges to create a product in 3scale. Administrator privileges are not required for other Solution Patterns.
customer-adminuser cannot prevent any user with access to the Solution Explorer from changing the Solution Pattern subscription settings. Any user with access to the Solution Explorer can determine which Solution Patterns are available in a cluster.
The following Solution Pattern is not available in this release:
- Low-code API development and SaaS integration
Ignore references to this Solution Pattern in the documentation.
Chapter 4. Deprecated features
- Support for TLS 1.0 and TLS 1.1 is removed from Red Hat Managed Integration. Only TLS 1.2 is supported as of this release.
Chapter 5. New and changed features
CodeReady Workspaces is upgraded to 2.0. Existing workspaces are not compatible with this version of CodeReady Workspaces.
Red Hat recommends that you recreate any existing workspaces using CodeReady Workspaces 2.0.
- In AMQ Online, rejected messages are retried indefinitely instead of being sent to the Dead Letter Queue.
- In AMQ Online, you can sort addresses by message count.
You can now configure AMQ Online.
If you plan to use AMQ Online in Managed Integration, you need to create an AMQ Online configuration for production. You must edit and apply YAML files using the command line (CLI) tools to configure AMQ Online.
This section provides general guidance on configuring AMQ Online for production usage in Managed Integration.
You are logged in to OpenShift as the
- You have experience with configuring AMQ Online.
Configure AMQ Online in Managed Integration as described in Configuring AMQ Online.
The name of the AMQ Online project in your cluster is
You must log in to the AMQ console as
- The name of the AMQ Online project in your cluster is
Configure your address space to use an external authentication service as shown in the address space example using an external authentication service.Note
The authentication services are configured by the AMQ Online service operator and are specified when creating an address space.
- You are logged in to OpenShift as the