Fix Readme
Abstract
IBM API Connect V5.0.8.6 is available. This update addresses several field APARs reported since the availability of API Connect v5.0.8.5 and v5.0.8.5-iFix.
Content
IBM API Connect V5.0.8.6 is now available. This update provides important development and APAR fixes.
We advise all users of IBM API Connect V5.0 to install this update to take advantage of the fixes.
Note: The Linux distribution for the Developer Portal OVA has moved from a Debian V7 base to an Ubuntu V16.04 base. Support for the Debian V7 OVA was withdrawn in May 2018. You are strongly encouraged to migrate your Developer Portal to the Ubuntu V16.04 base now, as support for Debian V7 upgrades was removed in May 2018.
Deprecation of IBM API Connect Micro Gateway Component on March 31, 2020:
IBM® API Connect Micro Gateway is deprecated in IBM API Connect Version 5.0.8 in favor of DataPower® Gateway. From 1 April 2020, Micro Gateway will no longer be supported.
Existing users can migrate their API definitions to IBM DataPower Gateways. For information on supported API policies, see Built-in policies.
Support life cycle policy for IBM API Connect Version 5.0.8.6:
IBM API Connect Version 5.0.8.x is a Long Term Supported (LTS) release and is a recommended product level for which support, including defect and security updates, will be provided through cumulative, in-place Fix Packs until the effective end of support (EOS) date for IBM API Connect Version 5.0. An LTS release is intended for customers that may need a longer-term deployment for their environment.
APAR fixes
The following APARs were addressed by IBM API Connect V5.0.8.6, along with other internally raised quality fixes:
| APAR | Summary |
| ALLOW AN INVOKE POLICY TO SEND A PAYLOAD ON A HTTP DELETE | |
| LI80346 | 'AUTOMATICALLY REFRESH EXTENSION ON GATEWAY SERVERS' IS GRAYED OUT AND CHECKED THE CHECK BOX IN DATAPOWER SERVICES ON CMC UI |
| LI80373 | CLOUD MANAGER TLS CLIENT DOESN'T PROVIDE CORRECT CERTIFICATES |
| LI80397 | API CONNECT INCORRECT CREDENTIALS CACHED BY POST-LOGIN PAGE |
| LI80431 | IN THE APIM EXPLORER, THE BASEPATH IS ABSENT FROM THE CURL COMMAND EXAMPLE, BUT VISIBLE IN THE OPERATION SECTION |
| LI80437 | RUNTIME STATUS CHANGE FOR OUTPUT OF "HA LIST" COMMAND |
| LI80451 | VALIDATION ERROR 204 THROWN WHEN EXECUTING VALIDATION POLICY ON RESPONSE |
| LI80517 | TAG HIERARCHIES DO NOT WORK AS EXPECTED |
| LI80518 | /TMP FILESYSTEM GETTING FILLED UP WITH ELASTICSEARCH JAVACORES AND HEMPDUMPS MAKING SYSTEM UNSTABLE. |
| LI80520 | APIC HTTP404 NOT FOUND: NO RESOURCES MATCH REQUESTED URI |
| LI80521 | AFTER UPGRADING TO 5.0.8.5, SUBSCRIPTIONS TO EXISTING PLANS STOP WORKING LEADING TO ERROR: "NOT REGISTERED TO A PLAN" |
| LI80523 | SOAP API CREATION: RESOLVE MESSAGE REFERENCE WITHIN TARGETNAMESPACE OF THE PORTTYPE |
| LI80536 | USER DEFINED POLICIES WITH GATEWAYSCRIPT ACTION MAY NOT HAVE ACCESS TO MESSAGE.BODY |
| LI80542 | REMOVE WARNING LOG MESSAGE CAUSED BY THE INVOKE POLICY RECEIVING A HTTP 204 RESPONSE |
| LI80548 | DELETED USERS GET ACCESS TO DEVELOPER ORGANIZATION |
| LI80557 | DELETING APP CREDENTIALS IN PORTAL RETURNS A WRONG MESSAGE IN NOTIFICATION |
| LI80585 | ANALYTICS MAPPINGS CAN FAIL AND CAUSE MISSING ANALYTICS DATA |
| LI80591 | EXTRA INFORMATION POSTED IN URL ERROR MSG WHEN USING UNSUPPORTED CHAR |
| LI80602 |
APIM-LOGS-MANAGEMENT--.ZIP POSTMORTEM LOGS ARE NOT CLEANED UP FROM IH_VAR CAUSING IH_VAR TO BE FILLED UP
|
| LI80614 | COM.JCRAFT.JSCH.JSCHEXCEPTION: ALGORITHM NEGOTIATION FAIL WHILE CREATING DEVELOPER PORTAL |
| LI80620 | CIRCULAR REFERENCES IN A JSON SCHEMA CAUSE THE VALIDATE POLICY TO FAIL |
| LI80621 | MICRO GATEWAY AUTO SHUTDOWNS |
| LI80628 | INCORRECT REDIRECTION POSSIBLE WITH BAD RSTATE IN OAUTH |
| LI80643 | API CONNECT V5.0.8.5 IS IMPACTED BY WEAK CRYPTOGRAPHIC ALGORITHMS |
| LI80650 | LOGSTASH CONFIG TEST EVENT FAILS TO STOP IT'S INSTANCE OF LOGSTASH |
| LI80653 | GETVARIABLE FUNCTION DOES NOT ALWAYS WORK WITH REQUEST PARAMETERS |
| LI80661 | NOTIFICATIONS ARE SHOWING USER INFORMATION WHEN YOU PUBLISH AN API BUT NOT WHEN YOU ARE REMOVING OR RETIRING IT |
| LI80662 | APP NAME NOT DISPLAYED IN ANALYTICS FOR MICROGATEWAY |
| LI80676 | CREATE SOAP API FROM WSDL WITH NO EXTERNAL REFERNCES FAILING IN API CONNECT |
| LI80680 | API CONNECT 5.0.8 PORTAL GENERATE_LOGS FAILS ERROR OCCURRED IN SCRIPT GENERATE_LOGS AT LINE: 225. |
| LI80698 | FIELDS WITH A DOT IN NAME ARE NOT MAPPED CORRECTLY - UI |
| LI80736 | IBM API CONNECT AFFECTED BY NODE.JS VULNERABILITIES |
| LI80743 | API CONNECT IMPACTED BY DRUPAL SA-CORE-2019-004 |
| LI80755 | MULTIPLE PHP VULNERABILITIES |
| LI81005 | OPENSSL VULNERABILITY |
Upgrade paths for API Connect:
For more information on IBM API Connect upgrade paths, see Supported Upgrade Paths.
There are specific validated upgrade paths between IBM® API Management Version 4.0 or later and IBM API Connect Version 5.0 or later. For more information, see Validated upgrade path for API Connect .
In addition to the specific validated upgrade paths for the API Management appliance, you must upgrade your IBM DataPower Gateway appliance. For more information, see Upgrading your DataPower appliances .
Upgrading the gateway to firmware level 7.5.0.1 is strongly recommended for the best experience.
Downloads:
Full installation and upgrade files for IBM API Connect Version 5.0.8.6 (Enterprise, Professional & Essentials) can be downloaded from Fix Central: IBM API Connect Version 5.0.8.6
Ensure that you have read and understood the upgrade and installation instructions before downloading and using the installation or upgrade files. You can find detailed installation instructions in IBM API Connect Knowledge Center -- Installing API Connect .
| What is Fix Central (FC)? |
Was this topic helpful?
Document Information
Modified date:
05 August 2019
UID
ibm10876536