News
Abstract
IBM API Connect V5.0.8.0 is available, which addresses several APARs, and includes product performance enhancements.
Content
IBM API Connect V5.0.8.0 is now available, which 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 is being 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 will be removed by May 2018.
Support lifecycle policy for IBM API Connect Version 5.0.8.0:
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.0, along with other internally raised quality fixes:
| APAR | Summary |
| LI79090 | ANALYTICS PORTAL REST APIS NOT AVAILABLE IN V5 |
| LI79382 | WHEN USING KOREAN WEB BROWSER TO ADD A NEW PLAN VIA UI, THE "NAME" FIELD OF THE PLAN IS NOT PRE-FILLED |
| LI79403 | REMOVING THEN ADDING A CONTROLLER DEFINITION FROM A COLLECTIVE SERVICE FAILS |
| LI79521 | UNABLE TO INVITE EXISTING USER TO ORG WHEN USING PORTAL DELEGATED USER REGISTRY (PDUR) |
| LI79534 | JSON-LISTENER LOGS FILL IH_VAR WHEN SYSTEM IS UP FOR A LONG TIME |
| LI79579 | UNABLE TO SELECT CONTEXT VARIABLE USING TYPE AHEAD "$(" WHEN DEFINING THE ENDPOINT URL |
| LI79586 | NO DEBUG DATA WHEN TESTING FROM API CONNECT TEST TOOL WITH HEADER APIM-DEBUG = TRUE |
| LI79603 | USERMANAGEMENT.INVALIDUSER ERROR WHEN INVITING AN USER TO A DEVELOPER PORTAL ORGANIZATION |
| LI79609 | CONFIGURING DESTINATION TARGETS FOR API CONNECT ANALYTICS DATA USING UDP SHOWS SUCCESS WHEN IT IS FAILING. |
| LI79631 | VALIDATE POLICY DOES NOT VALIDATE WSDL SOAP-ENVELOPE DATA |
| LI79635 | CUSTOM HEADERS ARE NOT INCLUDED IN ACCESS-CONTROL-EXPOSE-HEADERS |
| LI79657 | API CONNECT: PROPERTY VALUE IS ONLY 'ENCODED' WHILE 'ENCODE' CHECK BOX IS TICKED |
| LI79664 | ADDING GATEWAY SERVER TO GATEWAY SERVICE IN CMC FAILS WITH PROXY ERROR |
| LI79665 | IF THE MANAGEMENT SERVER GOES DOWN, BUFFERED ANALYTICS EVENTS ON THE GATEWAY MAY BE LOST PRIOR TO APIM RESTORE |
| LI79669 | CURRENT PASSWORD FIELD VALIDATION IS NOT WORKING |
| LI79670 | NAME AND SURNAME ARE SHOWN AS "NULL" BOTH IN DEVELOPER PORTAL AND API MANAGER USER INTERFACE. |
| LI79674 | PERFORMANCE PROBLEM WITH TAXONOMY TAGS V5 CONSUME CPU, SLOW, AND ERROR OUT. |
| LI79675 | UPGRADES IN API CONNECT TO ANY VERSION FAILS ON PURE SYSTEMS |
| LI79678 | SPURIOUS DP:PARSE() ERROR EVEN THOUGH API PERFORMS AS EXPECTED |
| LI79684 | USING MAP POLICY AND EXTRA NAMESPACE ADDED IN CHILD. |
| LI79687 | DURING UPGRADE MIGRATION TASK FAILS RUNNING OUT OF MEMORY |
| LI79696 | API CONNECT: OAUTH SCOPES ARE ALL LISTED IN EXPLORER EVEN IF OPERATION SPECIFIES LESS IN THE SWAGGER FILE |
| LI79698 | SWAGGER PROCESSING FAILS IF ORDER OF HASH CHANGES |
| LI79700 | CONSISTENT HIGH START LATENCY MAY BE EXPERIENCED IN CERTAIN SITUATIONS |
| LI79704 | XSD SUBSTITUTION AND ORIGINAL ELEMENT SAME NAME, EMIT BOTH |
| LI79707 | STUCKED AT "UNSAVED CHANGES DIALOG BOX" |
| LI79708 | WHEN SECURING AN API WITH OAUTH, A PROXY POLICY MAY INCORRECTLY APPEAR TO RETURN A HTTP 200 OK |
| LI79711 | XSLT POLICY MAY CHANGE CONTENT-TYPE FROM OTHER XML TYPE TO APPLICATION/XML |
| LI79712 | MAP CODE RESTRICTION NOT ALLOWING JSON OBJECTS IN VALUE STRINGS |
| LI79713 | IF 2 NICS CONFIGURED ANALYTICS PAGES SHOW ERRORS |
| LI79714 | CERTAIN POLICIES CHANGE INTEGER, BOOLEAN, OR NULL JSON ARRAYS TO STRING TYPE |
| LI79717 | IMAGES UPLOADED TO PORTAL ARE BROKEN OR NOT SEEN |
| LI79718 | WHILE UPDATING LDAP USER REGISTRY CREATED IN API MANAGER, HAVE TO RESTART THE GATEWAY SERVER TO REFLECT THE CHANGES IN API. |
| LI79719 | SOME CHARACTERS ARE NOT BEEN ABLE TO USE AS PASSWORD FOR CMC OR MANAGER CONSOLE |
| LI79724 | API CONNECT 5071 WITH LARGE NUMBERS OF PEOPLE IN LDAP SEARCH-AS-YOU-TYPE FEATURE CAUSES ERRORS |
| LI79726 | MAPPING REPEATING NODESET IN XML MISSING ELEMENTS |
| LI79727 | INFORMIX IS TIMEDOUT WITH THE APIC 5062 WITHOUT ANY KNOWN REASON |
| LI79728 | LIMITATION ON CHAR/STRING THAT CAN BE USED AS PASSWORD |
| LI79730 | IN A PRODUCT API ID SHOWS IN UI INSTEAD OF NAME |
| LI79733 | IF USING CHINESE TITLE FOR AN API, THE SAVE BUTTON STILL NOT ENABLED AFTER MAKING SOME CHANGES IN THE API |
| LI79735 | VALIDATE POLICY FAILS WHEN CHARSET IS IN CONTENT-TYPE HEADER |
| LI79736 | TOKEN STILL ISSUED WHEN REVOCATION ENDPOINT IS DOWN |
| LI79738 | PATH PARAMETERS ARE NOT BEING RESOLVED CORRECTLY |
| LI79743 | API CONNECT V5.0 APACHE HTTP SERVER VULNERABILITY |
| LI79744 | INCORRECT SAVE FUNCTION WHEN ADDING AUDIT LOG SETTINGS |
| LI79746 | HTTP RESPONSE STATUS 401 FOR A SUSPENDED CLIENT APP |
| LI79747 | POPULAR BLOCKS DO NOT SHOW TRANSLATED API OR PRODUCT DESCRIPTION |
| LI79749 | API CONNECT V5.0 JAVA VULNERABILITIES |
| LI79753 | X-SCOPEVALIDATE DEFINED WITHOUT REQUIRED URL PARAMETER RESULTS IN 404'S |
| LI79756 | INVOKE RESPONSE WITH A CONTENT-TYPE OF APPLICATION/JSON AND NO CONTENT CAUSES ERROR |
| LI79758 | BACKGROUND SYNC CAN CAUSE OUT OF MEMORY CONDITIONS IN PHP |
| LI79760 | DOUBLE-QUOTED STYLE MULTILINE STRING CAUSES ERROR |
| LI79761 | ABLE TO GENERATE TOKEN WHEN OAUTH PROVIDER API IS NOT SUBSCRIBED TO AN APPLICATION PLAN |
| LI79762 | ACCESSING WSDL DOCUMENT VIA ?WSDL FAILS WITH "ERROR OCCURRED WHILE VALIDATING WSDL \"\". MESSAGE: NULL" |
| LI79763 | WHEN ATTEMPTING A MIGRATION, THE NAME OF THE API OR PRODUCT DOES NOT APPEAR IN THE LIST |
| LI79764 | IN SOME CASES, THE ACCESS-CONTROL-EXPOSE-HEADERS DOES NOT CONTAIN THE LOCATION HEADER |
| LI79767 | OPERATION TAG DISPLAYED AS "ATTRIBUTE NAME NOT FOUND" |
| LI79769 | REQUIRED TO UPDATE OPENSSH IN A FORTHCOMING PORTAL VERSION |
| LI79772 | THE CONTENT-TYPE MAY CHANGE UNEXPECTEDLY WHEN PROXYING XML MTOM RESPONSE THROUGH API CONNECT |
| LI79773 | ENHANCEMENT TO MAP POLICY FOR IMPROVED PERFORMANCE |
| LI79777 | VISUALIZATIONS IN ANALYTICS DASHBOARD CHARTS SHOWS NO DATA |
| LI79780 | AFTER MIGRATION FROM V4 TO V5, TYPE OF DEFAULT VALUE CHANGED TO STRING IN MAP POLICY |
| LI79783 | API CONNECT PORTAL 5.X DRUPAL SECURITY ALERTS |
| LI79784 | DEV PORTAL RULES HTTP REQUEST MODULE ONLY WORKS WITH GET AND POST |
| LI79785 | API CONNECT CLICKJACKING VULNERABILITY |
| LI79786 | SWEET32 VULNERABILITY FOR IBM API CONNECT MANAGEMENT SERVER |
| LI79788 | APIC V5072 - ANALYTICS OFFLOAD NOT WORKING BEYOND 1 EVENT TYPE |
| LI79798 | API CONNECT V50X DEPENDENCY VULNERABILITY WARNINGS |
| LI79805 | API CONNECT V5.0 JAVA VULNERABILITIES |
| LI79816 | IN APIC 5.0.7.2 IE11 IN COMPATIBILITY VIEW MODE OFF RETURNS INCOMPLETE DIALOG BOXES IN DESIGN |
| LI79858 | SCIM REGISTRY : PASSWORD CHANGE FAILURE |
| LI79879 | IMPROVE THE PERFORMANCE OF FINDING APIS IN HUGE CATALOGS TO AVOID DATAPOWER GATEWAY TO TIME OUT |
| LI79937 | RATELIMIT REQUESTS FAIL WITH HTTP 500 ERROR CODE |
| LI80063 | API CONNECT APACHE HTTP SERVER VULNERABILITY (CVE-2014-0226) |
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.0 (Enterprise, Professional & Essentials) can be downloaded from Fix Central: IBM API Connect Version 5.0.8.0
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:
16 July 2018
UID
swg22008254