Release Notes

Red Hat Managed Integration 1

For Red Hat Managed Integration 1

Red Hat Customer Content Services


This document provides a high-level description of known issues and features in 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:



Red Hat Fuse Online

(Click Fuse Online Category)

Red Hat AMQ Online

(Click AMQ Online Category)

Red Hat 3scale API Management


Red Hat CodeReady Workspaces for OpenShift


Red Hat Single Sign-On


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 Error and 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 oauth-proxy and the oauth2 server.

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.
  • The customer-admin user 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 customer-admin user.
    • You have experience with configuring AMQ Online.


    1. Configure AMQ Online in Managed Integration as described in Configuring AMQ Online.

      • The name of the AMQ Online project in your cluster is openshift-enmasse.
      • You must log in to the AMQ console as customer-admin.
    2. Configure your address space to use an external authentication service as shown in the address space example using an external authentication service.


      The authentication services are configured by the AMQ Online service operator and are specified when creating an address space.

Legal Notice

Copyright © 2020 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 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.