News
Abstract
IBM API Connect V5.0.8.4 is available. This update addresses several APARs and includes product performance enhancements.
Content
IBM API Connect V5.0.8.4 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.
Support lifecycle policy for IBM API Connect Version 5.0.8.4:
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.4, along with other internally raised quality fixes:
| APAR | Summary |
| LI79926 | ELASTICSEARCH INDEX FOR ANALYTIC OFFLOADING MAY GET CREATED WITH INCORRECT SETTINGS |
| LI79957 | GHOST GATEWAY SERVICES MAY APPEAR IN CATALOG SETTINGS AFTER HAVING REMOVED THEM FROM THE CLOUD MANAGEMENT CONSOLE (CMC) |
| LI79966 | CANNOT RECOGNIZE WHICH PRODUCT IS SELECTED ON REPLACE/SUPERSEDE |
| LI79973 | SUPERSEDE/REPLACE PRODUCTS DOES NOT SHOW CORRECT INFO UNTIL BOTH ARE EXPANDED |
| LI79981 | CUSTOM ANALYTICS DASHBOARDS LOST AFTER UPGRADE TO V507X AND LATER |
| LI79996 | GATEWAY ENDPOINT ADDRESS IN APIM UI CANNOT BE EDITED PROPERLY |
| LI80000 | MISSING REDIRECT URL DOESN'T RETURN CORRECT ERROR |
| LI80009 | CUSTOM RATE LIMIT IS REMOVED WHEN A PLAN IS CHANGED TO INCLUDE ALL ROUTES (PATH) OF AN API VIA THE API DESIGNER UI |
|
LI80021 |
THE RESTORE_DEVPORTAL COMMAND FAILS IF THERE ARE UNEXPECTED FILES IN /VAR/AEGIR/BACKUPS |
| LI80027 | PASSWORD POLICY (MINIMUM LENGTH) SET IN DEVELOPER PORTAL IS NOT ENFORCED WHEN SETTING PASSWORD IN PASSWORD RESET PAGE |
| LI80035 | WHEN A USER DOES NOT HAVE CERTAIN PERMISSIONS, THE LANDING PAGE GIVES A PERMISSION ERROR |
| LI80061 | SETVARIABLE OF A MESSAGE HEADER WITH A PERIOD IN THE NAME FAILS |
| LI80065 | NOT ENOUGH INFORMATION IN AUDIT LOGGING |
| LI80071 | DEVELOPER PORTAL LOGIN SECURITY SETTINGS NOT EFFECTIVE |
| LI80077 | CLI COMMANDS TO EXTEND FILE SYSTEM AFTER ADDING DISK TO PORTAL ARE NOT NEEDED |
| LI80079 | IN CMC, RECEIVED ERROR WHEN TRYING TO DELETE A CERTIFICATE IN TLS PROFILE'S TRUST STORE |
| LI80083 | REMOVE DEVELOPER PORTAL ACCOUNT ALSO WIPES CMC AND APIM ACCOUNTS / ACCESS |
| LI80085 | 'FORCE PASSWORD CHANGE' IN CONFIGURATION > PEOPLE > PASSWORD POLICIES IS STILL AVAILABLE |
| LI80088 | APPROVAL LINK NOT DIRECTING TO CORRECT CATALOG / SPACE |
| LI80090 | APIC EMAIL ONLY USE TLSV1.0 |
| LI80091 | API CONNECT DEVELOPER PORTAL: DEFINITIONS IN API DOC ARE NOT HIGHLIGHTED WHEN THEIR NAME CONTAINS A HYPHEN |
| LI80094 | NO ANALYTICS AUDIT MESSAGE WHEN DEVELOPER ORGANISATION DELETED |
| LI80098 | INVALID ANALYTICS RESPONSE BODY DATA LOGGED AS API EVENT WHEN USING ASSEMBLY CATCHES |
| LI80105 | GETVARIABLE DOES NOT WORK FOR A REQUEST HEADER WITH A PERIOD IN ITS NAME |
| LI80107 | UNNECESSARY MESSAGE IS LOGGED ON SYSLOG WHEN WE CREATE NEW SPACE |
| LI80109 | INVOKE POLICY BACKEND RESPONSE WITH NO PAYLOAD AND NO CONTENT-TYPE COULD CAUSE XML PARSE ERROR |
| LI80110 | RATE LIMIT IN V5 IS NOT CONSISTENT WITH V4 |
| LI80111 | JWT-GENERATE POLICY ADD UNNECESSARY SINGLE QUOTATION ON EXP-CLAIM(VALIDITY PERIOD) PROPERTY |
| LI80113 | 'JSON PARSER LIMITS' NOT WORKING AS EXPECTED |
| LI80115 | WHEN SPACE IS ENABLED FOR A GIVEN CATALOG, USE DO NOT SEE THE CANCEL OPTION FOR THE PRODUCT PUBLISH APPROVAL REQUEST |
| LI80116 | INAPPROPRIATE OWNER NAME IS DISPLAYED IN AUDIT LOG WHEN CHANGING OWNER OF CATALOG/SPACE |
| LI80117 | PORTAL ANALYTICS PAGE SHOWS ERRORS FOR PDUR USERS |
| LI80118 | DEVELOPER PORTAL MISSING BASEPATH IN CALL EXAMPLE |
| LI80119 | A MAP POLICY WHOSE INPUT HAS A PROPERTY WITH A NULL VALUE WILL NOT MAP THAT PROPERTY TO AN OUTPUT DOCUMENT |
| LI80120 | APPROVALS URL SHOULD BE BUILT FROM / AND NOT FROM BACKEND DATA TO AVOID CORS ERROR DURING SUBSCRIPTION APPROVAL |
| LI80123 | PRODUCT LIST RETRIEVAL FAILS WITH 500 ERROR ON DEV PORTAL FOR NON-ADMIN USERS |
| LI80124 | PEERING GROUP OBJECT INCORRECTLY CONFIGURED WHEN USING DOCKER |
| LI80125 | WHEN RESET CLIENT SECRET IN DEVELOPER PORTAL, APPLICATION NAME AND ID ARE NOT CORRECTLY DISPLAYED IN JAPANESE AUDIT LOG |
| LI80126 | WHEN ADDING AN APPLICATION'S CREDENTIALS IN DEVELOPER PORTAL, ITS NAME AND ID ARE NOT CORRECTLY DISPLAYED IN AUDIT LOG |
| LI80130 | UNABLE TO DISABLE TWO FACTOR AUTHENTICATION IN DEVELOPER PORTAL |
| LI80131 | EXTRA WARNING REPORTED BY API VALIDATION FOR DEFINITION REFERENCING OTHER DEFINITIONS |
| LI80132 | SPACE NAME AND CATALOG NAME ARE NOT DISPLAYED CORRECTLY IN PUBLISH NOTIFICATION |
| LI80133 | NO HIGHLIGHTING OF EXAMPLE REQUESTS IN PORTAL |
| LI80135 | AS PRODUCT MANAGER WHO IS INVITED JUST TO A SPACE, THE SUBSCRIPTION CREATION FAILED WITH PERMISSION ERROR |
| LI80137 | MAP POLICY ACTIONS IN THE API FOR POLYMORPHIC XML ARRAY OUTPUT ARE NOT CREATED PROPERLY |
| LI80138 | USERS WITH ADMIN ROLE SEE ‘DELETE ACCOUNT’ LINK ON OTHER USERS |
| LI80143 | AN INVOKE POLICY WITH A WEB SERVICE BACKEND THAT RETURNS A SOAP FAULT RESPONSE WILL NOT DRIVE A POST-ERROR EXTENSION RULE |
| LI80145 | A MAP POLICY WHOSE JSON OUTPUT SCHEMA HAS A REQUIRED PROPERTY MAY PRODUCE INCORRECT JSON OUTPUT |
| LI80149 | EMPTY STRING RETURNED WHEN USING CONTEXT VARIABLE MESSAGE.BODY VALUE |
| LI80150 | 'APIM:ERROR' TEMPLATE DOES NOT REPORT DECLARED ERROR IN XSLT POLICY |
| LI80151 | JSON PARSE NOT WORKING WITH INPUT PARAMETER |
| LI80152 | USING V5083 BUT UI DISPLAY API CONNECT HAS BEEN UPGRADED TO VERSION "5.0.8.0" IN CHINESE BROWSERS |
| LI80155 | APIC DEVELOPER PORTAL FAILS TO START, WITH DB ERROR |
| LI80156 | API CONNECT 5.0.8.3 DEVELOPER PORTAL URIS IN EXAMPLE RESPONSE CONTAIN EXTRA SLASH '/' CHARACTERS |
| LI80157 | API CONNECT 5.0.8.1. AFTER REPLACE-PRODUCT COMMAND IS RUN, SOME API'S ARE TAKEN OFFLINE. |
| LI80159 | GENERIC ERROR MESSAGE WHEN X-IBM-CLIENT-ID AND SECRET HEADERS ARE MISSING |
| LI80160 | DUPLICATE APIS ARE LISTED IN THE SEARCH RESULTS OF THE DEVELOPER PORTAL |
| LI80161 | A MAP POLICY JAVASCRIPT VALUE STRINGS REFERENCING A VARIABLE WITH AN @ IN THE VARIABLE NAME WILL NOT RETURN A VALUE |
| LI80164 | USERNAME IS NOT SHOWING THE CORRECT EXPECTED ONE ON AUDIT LOG |
| LI80165 | MAP XML OUTPUT IS NOT GENERATING XSI:NIL ATTRIBUTE FOR REQUIRED STRING ELEMENTS |
| LI80166 | THE MAP POLICY DOES NOT INCLUDE A NAMESPACE IN THE XSI:TYPE ATTRIBUTE VALUE IN SOME CASES |
| LI80168 | AFTER UPGRADE TO API CONNECT PORTAL 5.0.8.3 ,CLIENTS ARE NOT ABLE TO RESET PASSWORD, PAGE GETS STUCK ON PASSWORD IS EXPIRED |
| LI80169 | ROUTER CLIENT SETS HTTPSPORT VALUE INCORRECTLY |
| LI80176 | APIM.GETVARIABLE OF A REQUEST PARAMETER MAY NOT BE URL-DECODED BY DEFAULT |
| LI80177 | ACCESSING A DASHBOARD IN BROWSER IT FAILS AFTER UPGRADING APICONECT TO 5.0.8.2 FROM 5.0.6.3 |
| LI80178 | USING A CONFIG BACKUP TAKEN FROM DEBIAN PORTAL INTO UBUNTU PORTAL, SET_NTP -S MIGHT WRONGLY RETURN NO NTP CONFIGURED |
| LI80180 | AFTER UPGRADING PORTAL TO V5083, GETTING ERROR CREATING PDUR USER ACCOUNT |
| LI80183 | THE OWNER CHANGE OF DEVELOPER ORG IS NOT LOGGED ON ANALYTICS AUDIT LOG |
| LI80191 | ERRORS DEFINED WITHIN AN OTHERWISE CASE OF A SWITCH DOESN'T SHOW UP IN A CATCH |
| LI80194 | PHP_MAX_MEMORY, UPLOAD_MAX_SIZE, AND SET_TIMEZONE COMMANDS FAIL AFTER 5083 IFIX UPGRADE |
| LI80197 | CONSUMES TYPE FOR API DOES NOT DISPLAY ON THE DEVELOPER PORTAL |
| LI80263 | PORTAL USER REGISTRATION LINK NOT ABLE TO OPEN AFTER UPGRADE TO V5083 |
| LI80737 | CALLS TO OAUTH PASSWORD GRANT TYPE FAILS BECAUSE OF DUPLICATE PARAMETER 'CLIENT_ID' |
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.4 (Enterprise, Professional & Essentials) can be downloaded from Fix Central: IBM API Connect Version 5.0.8.4
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:
27 March 2019
UID
ibm10715781