News
Abstract
IBM API Connect V2018.4.1.8-iFix2.0 is now available. This update includes important internal development and field reported fixes.
Content
IBM API Connect 2018.x delivers enhanced capabilities for the market-leading IBM API Management solution. In addition to the ability to deploy in complex, multi-cloud topologies, this version provides enhanced experiences for developers and cloud administrators at organizations.
The API Connect 2018.4.1.8-iFix2.0 update includes important internal development and field reported fixes.
A special note on upgrades from prior versions of API Connect v2018.4.1.x: API Connect v2018.4.1.5 is now a prerequisite for API Connect v2018.4.1.8-iFix2.0 for VMWare (.OVA) deployments. You cannot upgrade your API Connect topology to 2018.4.1.8-iFix2.0 without first being at the v2018.4.1.5 level. Again, this restriction applies only to VMWare (.OVA) deployments only of IBM API Connect v2018.4.1.8-iFix2.0. This is due to the level of Kubernetes deployed with the VMWare (.OVA) installation of IBM API Connect v2018.4.1.8-iFix2.0 and restrictions around skipping levels of Kubernetes when upgrading.
See the "What's New" topic in the IBM Knowledge Center for more information on new features included in API Connect v2018.4.1.8-iFix2.0.
API Connect v2018.4.1.8-iFix2.0 contains the following field reported APARs:
| APAR | Summary |
| LI80718 | WHEN SUBSCRIBING AN APPLICATION IN THE PORTAL, THERE IS PROBLEM IF CREATING MULTIPLE NEW APPLICATIONS |
| LI80769 | CANNOT EDIT OBJECT DEFINITIONS IN API MANAGER UI |
| LI80781 | SOME API CONNECT 2018 MANAGEMENT SERVER SCREENS SHOW POOR PERFORMANCE |
| LI80803 | API CONNECT 2018.4.1.3 ASSEMBLY SWITCH LOGIC IS ERASED WHILE EDITING API ASSEMBLY |
| LI80893 | API MANAGER "DESIGN" VIEW AFTER SELECT VALUES AS TYPE INTEGER AND CLICK SAVE, IN THE "SOURCE" VIEW IT BECOME TYPE: LONG |
| LI80948 | CHANGING OAUTH NATIVE PROVIDER TITLE, FROM THE UI, MAY LEAD TO INVALID OAUTH CONFIGURATION |
| LI80950 | SPECIAL CHARACTERS IN "REASON FOR DECLINING" ARE NOT ENCODED CORRECTLY |
| LI80951 | MGMT TO PORTAL/GATEWAY SYNC FAILURE - BAD SNAPSHOT |
| LI80959 | APP NAME NOT VISIBLE IN SUBSCRIPTION EMAIL |
| LI80969 | POPULATING API PROPERTY WITH VALUE FROM CATALOG PROPERTY FAILS INTERMITTENTLY |
| LI80972 | UNABLE TO ADD GATEWAY SERVICE TO CATALOG AFTER NETWORK OUTAGE |
| LI80985 | WHEN ADDING SECURITY DEFINITION IN API AFTER SELECT OAUTH2 AND CLICK SAVE A WARNING MESSAGE SHOWS UP |
| LI80989 | GATEWAY IS PARSING THE PAYLOAD WHEN THE REDACT POLICY IS FOR LOGS ONLY. |
| LI80990 | ISSUE WITH BASEPATH WHEN ACTIVATING API FROM EXISTING WSDL SERVICE (SOAP PROXY) AT CREATION TIME. |
| LI80991 | ISSUE WITH BASEPATH WHEN CREATING AN API FROM EXISTING WSDL SERVICE (SOAP PROXY) |
| LI80998 | UNABLE GET OAUTH TOKEN IN API MANAGER ASSEMBLY WITH APPLICATION FLOW |
| LI81000 | CANNOT IMPORT AN API YAML WHICH IS GENERATED FROM A WSDL |
| LI81001 | THE USERNAME IS DISPLAYED AS "UNDEFINED" ON THE PORTAL AFTER LOGIN USING OIDC REGISTRY |
| LI81007 | CREATING A NEW API FROM WSDL FAILS WITH THIS IS A VIOLATION OF A WS-I RULE MESSAGE IN API SOURCE VIEW |
| LI81008 | ALLOW RESET OF PASSWORD WHEN EMAIL/NOTIFICATION IS NOT CONFIGURED |
| LI81010 |
TRANSFER OWNERSHIP FOR CONSUMER ORG ADMINISTRATIVELY NOT WORKING
|
| LI81020 | RESOLVE $(CATALOG.URL) IN TEST TOOL FOR OAUTH APIS |
| LI81021 | VALIDATE ACTION WILL FAIL IF DEFINITION CONTAINS SPACES |
| LI81025 | FOR THE APIS ON PORTAL, AT OPERATION LEVEL ALL THE OAUTH SCOPES ARE DISPLAYED INSTEAD OF THE ACTUAL SELECTED ONE |
| LI81027 | MAP MISSING XML OUTPUT WITH A COMPLEX CIRCULAR REFERENCING SCHEMA |
| LI81028 | GATEWAY/MGMT SYNC NOT RECOVERING AFTER CONNECTION FAILURES |
| LI81031 | PUBLISHED APIS NOT AVAILABLE ON GATEWAY - SYNC UNDEFINED IDS |
| LI81037 | RACE CONDITION CAN PREVENT THE TASK MANAGER FROM RUNNING - SYNC |
| LI81038 | OAUTH SCOPES PRESENT IN THE SOURCE CODE ARE NOT SEEN IN THE USER INTERFACE |
| LI81041 | AN XML INPUT MAPPING TO A JSON OUTPUT MAY PRODUCE BADGERFISH SYNTAX AFTER UPGRADING TO VERSION 5.0.8.7. |
| LI81043 | ERROR: A SECURITY SCHEME CALLED NAMEA HAS NOT BEEN DEFINED |
| LI81047 | API CONNECT V5 INVOKE POLICY ERROR RESPONSES NOT COMPATIBLE WITH APIM V4 |
| LI81048 | ERROR PUBSLISHING API WITH CUSTOM NAME FOR THE API KEY AS SECURITY DEFINTION |
| LI81050 | IMPROVE CASSANDRA RESTORE PROCESS ON SLOWER ENVIRONMENTS |
| LI81052 | ANALYTICS RESPONSE_BODY IS NOT POPULATED FOR SOME SOAP ERROR RESPONSES |
| LI81057 | GATEWAY WILL FAIL TO PUBLISH DUE TO CONTROL CHARACTERS IN THE CATALOG METADATA |
| LI81160 | APIC DESKTOP DESIGNER - UNABLE TO IMPORT OPENAPI SPEC DUE TO ERROR - CANNOT READ PROPERTY 'INFO' OF UNDEFINED |
| LI81062 | PRODUCT DELETE EVENT IS NOT GETTING GENERATED AS PART OF PRODUCT REPLACE - SYNC |
| LI81069 | UNEXPECTED URL QUERY PARAMETER WHEN SWITCHING PORTAL LANGUAGES |
| LI81072 |
UNABLE TO UPDATE CATALOG CONFIGURATION WITH 500 API ERROR
|
| LI81073 | IMPROVEMENTS AND BUG FIXES IN BACKUP AND REPAIR CRON JOBS CREATED BY CASSANDRA OPERATOR |
| LI81074 | MAP POLICY MAY GENERATE EMPTY XML ELEMENTS FOR NON REQUIRED ELEMENTS |
| LI81075 | WSDL ENDPOINT LOCATION NOT REPLACED FOR CERTAIN NON ENGLISH LANGUAGE |
| LI81086 | NON-ASCII CHARACTERS IN THE API DESCRIPTION NOT DISPLAYED CORRECTLY |
| LI81090 | MANAGEMENT SERVER OOM ERROR DURING SYNC - EVENT QUEUES |
| LI81091 | THE HOOK_APP_CREATE HOOK IS BEING TRIGGERED AS PART OF APPLICATION DELETION |
| LI81092 | THE HOOK PAYLOAD TRIGGERED FOR APPLICATION CREATION SOMETIMES DOES NOT INCLUDE THE CLIENT SECRET |
| LI81094 | INPUT XML WITH REPEATING ELEMENTS USING A DIFFERENT NAMESPACE PREFIX WILL NOT MAP PROPERLY |
| LI81096 | API CONNECT CONTEXT VARIABLES ARE EMPTY |
| LI81098 | THE "COPY" BUTTON IN THE SCHEMA TAB IN THE DEVELOPER PORTAL DOESN'T WORK. |
| LI81099 | MANAGEMENT SERVER BACKUP FILE SIZE OPTIMIZATIONS |
| LI81104 | AUTO COMPLETE IS ENABLED IN CLOUD MANAGEMENT AND API MANAGER LOGIN PAGE'S PASSWORD FIELD |
| LI81106 |
MANAGEMENT SUBSYSTEM ALLOWS TLSV1.0 ON PORT 7001
|
| LI81108 | AFTER UPGRADE, APIM WITH UPGRADE STAGE REMAIN AT CONTROLPANE |
| LI81111 | INCORRECT ERROR DISPLAY DURING PASSWORD RESET FOR CERTAIN CLASSES OF USER |
| LI81113 | X-POWERED-BY HEADER EXPOSES PHP VERSION |
| LI81116 | LONG MAXLENGTH STRING EXAMPLE IN PORTAL CAUSES MEMORY EXHAUSTION IN BROWSER |
| LI81117 | AFTER UPGRADING API CONNECT TO VERSION 2018.4.1.6, CANNOT MODIFY PRE-EXISITNG OAUTH PROVIDER |
| LI81121 | REPLACE APPROVAL TASK RETURN ERROR |
| LI81122 | UNRESPONSIVE INGRESS CONTROLLER WHILE BEHIND A LOAD BALANCER |
| LI81123 | PROVIDE NEW FUNCTION TO ACCESS EXCEPTION DATA IN A CATCH |
| LI81125 | API WITH MARKDOWN IN THE DESCRIPTION IS NOT DISPLAYING CORRECTLY |
| LI81127 | CONTENT TYPE CHARSET SETTING LOST AFTER REDACTION POLICY |
| LI81134 |
SERVER CREDENTIAL VALIDATION NOT ENABLED DESPITE A TRUSTSTORE BEING PROVIDED.
|
| LI81139 | MULTIPLE WEBHOOK EVENTS CAN BE CREATED WITH THE PREVIOUS ID - SYNC |
| LI81140 | APIM MANAGER MAY NOT BE ABLE TO PROCESS TASKS ANYMORE - SYNC |
| LI81172 | API MANAGER V2018.4.1.8 API PUBLISHES CAN FAIL - DUPLICATE WEBHOOK EVENTS - SYNC |
| LI81180 | MANUALLY EDITING VERSION FIELD ON DRAFTS VIEW CREATES AN API WITH VALIDATION ERRORS |
| LI81292 | LOGSTASH CVE-2019-7612 |
| LI81327 | APIM BECAUSE SLOW AFTER A WHILE |
*** Note that links to some security related APARs may not be available in the table above. This is intentional for security purposes. ***
Database technology used in this release:
IBM API Connect relies on SQL and no-SQL database technology to provide persistent storage of objects required for the function of the product. Database technology requires fast and reliable storage and in the case of a highly available configuration, the database must perform adequately in a clustered configuration.
GlusterFS: Testing of IBM API Connect when using GlusterFS has shown that GlusterFS does not provide the speed or reliability for any of the database technologies used in IBM API Connect and thus should not be considered for use as the clustered storage facility with this product.
AWS EBS: IBM API Connect deployed on Kubernetes in EC2 instances on AWS should make use of the AWS EBS storage solution with GP2 or IO1 type.
Important note on upgrading to 2018.4.1.8-iFix2.0:
When upgrading to Version 2018.4.1.8 iFix 2 or later, you must complete a manual backup just before starting the upgrade. The manual backup is required because the upgrade can take an extended period of time. See Requirements for upgrading on VMware and Requirements for upgrading on Kubernetes.
We advise all users of prior version of API Connect v2018.x to install this update to take advantage of the fixes.
For more information about this release, see API Connect Knowledge Center: What's new in this release.
Support lifecycle policy for IBM API Connect Version 2018.4.1.8-iFix2.0:
IBM API Connect 2018.4.1.8-iFix2.0 is fixpack to a Long-Term Supported (LTS) release. API Connect 2018.4.1.8-iFix2.0 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 service (EOS) date for IBM API Connect 2018.4.1.x. An LTS release is intended for customers that may need a longer-term deployment for their environment. For more information, see IBM API Connect v2018.x Support Lifecycle.
Downloads:
Full installation files for IBM API Connect 2018.4.1.8-iFix2.0 and the IBM API Connect 2018.4.1.8-iFix2.0 Toolkit files can be downloaded from Fix Central :
| Description – Filename | Date Published |
|
IBM API Connect Management V2018.4.1.8-iFix2.0 Containers
|
21 November 2019 |
|
IBM API Connect Developer Portal V2018.4.1.8-iFix2.0 Containers
|
21 November 2019 |
|
IBM API Connect Analytics V2018.4.1.8-iFix2.0 Containers
|
21 November 2019 |
|
IBM API Connect Management V2018.4.1.8-iFix2.0 for VMWare
|
21 November 2019 |
|
IBM API Connect Developer Portal V2018.4.1.8-iFix2.0 for VMWare
|
21 November 2019 |
|
IBM API Connect Analytics V2018.4.1.8-iFix2.0 for VMWare
|
21 November 2019 |
|
IBM API Connect Install Assist V2018.4.1.8-iFix2.0 for Linux
|
21 November 2019 |
|
IBM API Connect Install Assist V2018.4.1.8-iFix2.0 for Mac
|
21 November 2019 |
|
IBM API Connect Install Assist V2018.4.1.8-iFix2.0 for Windows
|
21 November 2019 |
|
IBM API Connect Toolkit V2018.4.1.8-iFix2.0 for Linux
|
21 November 2019 |
|
IBM API Connect Toolkit V2018.4.1.8-iFix2.0 for Mac
|
21 November 2019 |
|
IBM API Connect Toolkit V2018.4.1.8-iFix2.0 for Windows
|
21 November 2019 |
|
IBM API Connect Toolkit Designer with Loopback V2018.4.1.8-iFix2.0 for Linux
|
21 November 2019 |
|
IBM API Connect Toolkit Designer with Loopback V2018.4.1.8-iFix2.0 for Mac
|
21 November 2019 |
|
IBM API Connect Toolkit Designer with Loopback V2018.4.1.8-iFix2.0 for Windows
|
21 November 2019 |
|
IBM API Connect V2018.4.1.8-iFix2.0 Analytics.OVA Upgrade File
|
21 November 2019 |
|
IBM API Connect V2018.4.1.8-iFix2.0 Management Server.OVA Upgrade File
|
21 November 2019 |
|
IBM API Connect V2018.4.1.8-iFix2.0 Developer Portal.OVA Upgrade File
|
21 November 2019 |
| IBM DataPower Gateway for Docker Production Edition v2018.4.1.8r idg_dk2018418r.lts.prod.tar.gz |
21 November 2019 |
| IBM DataPower Gateway for Docker Non-Production Edition v2018.4.1.8r idg_dk2018418r.lts.nonprod.tar.gz |
21 November 2019 |
|
Kubernetes DataPower Monitor v2018.4.1.8r
|
21 November 2019 |
Ensure that you have read and understood the installation instructions for OVAs and Containers before downloading and using the installation files. You can find detailed installation instructions in IBM API Connect Knowledge Center -- Installing API Connect
Beginning with API Connect v2018.4.1.4, files for ICP Installation will be provided outside of the main fix pack availability but generally within a week of the fix pack, or subsequent iFix, availability date. See the table below for the availability and download links from Fix Central.
ICP Installation Files for API Connect v2018.4.1.8-ifix2.0
| Description – Filename | Date Published |
| IBM API Connect ICP Enterprise V2018.4.1.8-iFix2.0 IBM_API_Connect_ICP_Enterprise_2018.4.1.8-iFix2.0.zip |
21 November 2019 |
| IBM API Connect ICP Professional V2018.4.1.8-iFix2.0 IBM_API_Connect_ICP_Professional_2018.4.1.8-iFix2.0.zip |
21 November 2019 |
IBM API Connect Local Test Environment is now available
The IBM API Connect Local Test Environment allows you to test APIs on your local machine, without the need to connect to an API Connect management server. For more details, see the IBM API Connect Knowledge Center
| Description – Filename | Date Published |
| IBM API Connect Local Test Environment apic-lte-2018.4.1.8-ifix2.0.zip |
21 November 2019 |
Was this topic helpful?
Document Information
Modified date:
17 February 2020
UID
ibm11088182