Fix Readme
Abstract
IBM API Connect V5.0.8.8-iFix2 is available. This update addresses a number of field APARs reported since the availability of API Connect v5.0.8.8-iFix1.
Content
IBM API Connect V5.0.8.8-iFix2 is now available to address internal fixes and customer APARs reported since API Connect v5.0.8.8. We advise all users of IBM API Connect V5.0 to install this update to take advantage of the fixes.
An important note for customers who leverage API Connect v5 analytics before upgrading to 5.0.8.8-iFix2: A one time upgrade step is required to retain analytics data during the upgrade window when updating to 5087-ifix4 or later, see the following link for details: https://www.ibm.com/support/knowledgecenter/SSMNED_5.0.0/com.ibm.apic.install.doc/prereq_5087ifix4_dpgw_certs.html
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 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 31 March 2020:
IBM® API Connect Micro Gateway was 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 lifecycle policy for IBM API Connect Version 5.0.8.8-iFix2:
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 fixpacks until the effective end of support (EOS) date for IBM API Connect Version 5.0. An LTS release is intended for customers that might need a longer-term deployment for their environment.
APAR fixes
The following APARs are addressed by IBM API Connect V5.0.8.8, along with other internally raised quality fixes:
| APAR | SUMMARY |
| LI80192 | IN MAP "EXTENSION TYPE" DROP DOWN, EXPECTED ALLOF SECTIONS NOT PRESENT |
| LI80612 | WHEN CREATING OAUTH PROVIDER, ENDPOINT DOCUMENTATION IS GENERATED INCORRECTLY |
| LI80869 | OUTPUT OF ´TIME SHOW´ COMMAND REPORTS INCORRECT VALUE FOR "HOST TIME (UTC)" |
| LI80989 | GATEWAY IS PARSING THE PAYLOAD WHEN THE REDACT POLICY IS FOR LOGS ONLY |
| LI81021 | VALIDATE ACTION WILL FAIL IF DEFINITION CONTAINS SPACES |
| LI81057 | GATEWAY WILL FAIL TO PUBLISH DUE TO CONTROL CHARACTERS IN THE CATALOG METADATA |
| LI81084 | UPDATES TO USER NAME COMPLETION IN DEVELOPER PORTAL |
| LI81119 | QUERY PARAMETER ENUM OF TYPE INTEGER IS NOT SHOWN WHEN TESTING IN PORTAL UI |
| LI81123 | PROVIDE NEW FUNCTION TO ACCESS EXCEPTION DATA IN A CATCH |
| LI81127 | CONTENT TYPE CHARSET SETTING LOST AFTER REDACTION POLICY |
| LI81146 | MAP SET ACTION WITH A DEFAULT OF NULL DOES NOT USE THE API PROPERTY TO ENABLE NULL MAPPED VALUES |
| LI81148 | HIGH PROFILE TO SPEED UP POLICY DEPLOY PERFORMANCE |
| LI81159 | A CONNECTIONERROR ON A PROXIED WEB SERVICE REQUEST WILL NOT RETURN AN ERROR RESPONSE |
| LI81162 | INCONSISTENCIES WHEN USING MICROGATEWAY WHEN FILTERING ANALYTICS |
| LI81164 | API CONNECT TOOLKIT VERSION 5.0.8.7 HAS REMOVED THE FUNCTIONALITY TO TEST API LOCALLY |
| LI81176 | 204 RESPONSE WITH NO PAYLOAD GETS PARSE ERROR WHEN RESPONSE INCLUDES CONTENT-TYPE |
| LI81250 | MULTIPLE SIMULTANEOUS GATEWAY REFRESHES MAY RESULT IN ERRONEOUS SLM PEERING CONFIGURATION |
| LI81257 | THE MAP POLICY MAY EXHIBIT ADDITIONAL LATENCY FOR SOME APIS |
| LI81303 | VALIDATE POLICY INCORRECTLY FAILS XML VALIDATION IN SOME CASES |
| LI81311 | VALIDATE POLICY XML VALIDATION MAY FAIL FOR VALID XML |
| LI81323 |
MAP POLICY ACTION'S DEFAULT PROPERTY DOESN'T ALLOW VARIABLE RESOLUTION FOR INTEGER OUTPUT PROPERTIES
|
| LI81326 | GATEWAYSCRIPT POLICIES WITHIN LARGE APIS THAT USE MULTIPLE GETVARIABLE OR GETCONTEXT FUNCTION CALLS MAY BE LATENT |
| LI81333 | A PAYLOAD ON AN OPTIONS CALL ECHOES BACK ON THE RESPONSE |
| LI81342 | IN DEVELOPER PORTAL UI UNABLE TO ADD ADDITIONAL USERS TO A DEVELOPER ORG |
| LI81357 | MAP POLICY FAILS TO MAP SOME XML INPUT ELEMENTS |
| LI81362 | WSDL IMPORT ERROR WHEN USING RELATIVE IMPORT PATH FOR WSDL AND XSD FILES |
| LI81364 | IMPROVED PERFORMANCE ON CATALOG>SPACE>PRODUCTS SCREEN |
| LI81375 | INVOKE POLICY MAY FAIL IN SOME CASES WHEN THE OUTPUT VARIABLE SPECIFIED IS MESSAGE |
| LI81391 | MAP POLICY WITH XML INPUT AND A SET ACTION WITH A FOREACH WHERE THE FOREACH ELEMENT IS NOT REPEATING WILL FAIL TO MAP |
| LI81393 | MIGRATING SUBSCRIPTIONS MAY TIMEOUT |
| LI81394 | LISTING PRODUCTS IN A SPACE TAKES LONG TIME OR TIMES OUT |
| LI81398 | CONCURRENT GATEWAY ADDITION FEATURE |
| LI81413 | VALIDATE APPS CLIENTID |
| LI81418 | UNABLE TO PUBLISH PRODUCTS AFTER PULLED FROM CLI WITH MORE THEN ONE APIS ADDED IN THE PRODUCT |
| LI81421 | DEV PORTAL INVITED USER EMAIL ADDRESS ACCEPTS WHITE-SPACE |
| LI81438 | A PUBLISH WITH AN INVALID XML CHARACTER IN SOME CATALOG OR API METADATA COULD INVALIDATE THE ENTIRE CATALOG AT THE GATEWAY |
| LI81440 | IT IS NOT POSSIBLE TO ADD SPACES IN THE VALUES OF A HEADER |
| LI81447 | INVOKE POLICY FAILS IF RESPONSE HAS A CONTENT TYPE FOR AN XLSX DOCUMENT |
| LI81452 | GATEWAYSCRIPT CODE WITH AN ESCAPED BACKSLASH IN SOURCE WILL HAVE THE CODE CHANGED TO ELIMINATE ONE OF THOSE BACKSLASHES |
| LI81453 | BLANK API DESIGNER UI IN IE 11 |
| LI81490 | DISABLE CORS HEADERS ON ERROR |
| APAR | SUMMARY |
| LI81461 | EXPLORING THE API DOES NOT WORK WHEN THE API PUBLISHED WITH THE OAUTH2 SECURITY DEFINITION |
| LI81469 | DEVELOPER PORTAL'S API TEST TOOL DOESN'T WORK PROPERLY IN INTERNET EXPLORER 11 |
| DATAPOWER DOMAIN IS NOT SAVED WHEN A USER DEFINED POLICY IS IMPORTED TO A CATALOG | |
| LI81509 | PAGINATION MISSING FROM COMMUNITY APPLICATIONS PAGE |
| APAR | SUMMARY |
| LI81379 | ICMP TO BE ADDED ON FIREWALL REQUIREMENT |
| LI81516 | V5C GATEWAY IS INCORRECTLY SENDING API CONNECT'S APP CLIENT ID |
| LI80520 | DRUPAL SA-CORE-2020-003 |
| LI81522 | DRUPAL SA-CORE-2020-002 |
| LI81526 | V5.0.8.8IFIX1 APIC TOOLKIT DOESN?T WORK ANYMORE FOR LISTING PRODUCTS IN A SPACE ENABLED CATALOG |
| LI81527 | ERROR WHEN MIGRATING SUBSCRIPTIONS ON A PRODUCT WITH DISABLED VISIBILITY |
| LI81528 | INCREASE WAIT TIME BEFORE REFRESHING GATEWAYS |
| LI81534 | API CONNECT CVE-2020-4251 |
| LI81535 | PHP CVE-2020-7064 CVE-2020-7065 CVE-2020-7066 |
| LI81584 | CROSS-SITE REQUEST FORGERY (CVE-2020-13663) |
| LI81586 | DRUPAL (SA-CONTRIB-2020-025) |
| LI81613 | PHP CVE-2019-11048 |
| LI81627 | PHP CVE-2020-7067 |
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
Refer to the life-cycle support page for the IBM DataPower Gateway
Downloads:
Full installation and upgrade files for IBM API Connect Version 5.0.8.8-iFix2 can be downloaded from Fix Central: IBM API Connect Version 5.0.8.8-iFix2
A one time upgrade step is required to retain analytics data during the upgrade window when updating to 5087 ifix 4 or later. See the following link for details: https://www.ibm.com/support/knowledgecenter/SSMNED_5.0.0/com.ibm.apic.install.doc/prereq_5087ifix4_dpgw_certs.html
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:
12 November 2020
UID
ibm16202443