News
Abstract
IBM API Connect V2018.4.1.10 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.10 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.10 for VMWare (.OVA) deployments. You cannot upgrade your API Connect topology to 2018.4.1.10 without first being at least at the v2018.4.1.5 level. Again, this restriction applies only to VMWare (.OVA) deployments only of IBM API Connect v2018.4.1.9. This is due to the level of Kubernetes deployed with the VMWare (.OVA) installation of IBM API Connect v2018.4.1.10 and restrictions around skipping levels of Kubernetes when upgrading. Additionally, a Control Plane file is required if you are upgrading from v2018.4.1.5 or v2018.4.1.6 to v2018.4.1.10 (VMWARE .OVA only). Reference the Upgrade Instructions page in the API Connect IBM Knowledge Center.
An additional note on upgrade procedures for DataPower Gateway high-availability clusters.
The upgrade procedure for DataPower Gateway has new steps for upgrading high-availability clusters, to ensure that a single gateway is running as primary for all gateway-peering definitions, and that the primary gateway is upgraded last. See the "What's New" topic in the API Connect IBM Knowledge Center for more information on this and new features included in API Connect v2018.4.1.10.
API Connect v2018.4.1.10 contains the following field reported APARs:
| APAR | Summary |
| LI80674 | API CONNECT 2018.4.1.3 PORTAL ERROR MESSAGES AND NOTIFICATIONS ARE DISPLAYED IN ENGLISH-ONLY |
| LI80976 | APIM ENDPOINT ALLOWS ACCESS TO /ADMIN UI |
| LI81103 | PORTAL SIGN-UP NOTIFICATION EMAIL USES THE SENDER NAME AND EMAIL THAT WAS CONFIGURED IN CLOUD MANAGER INSTEAD OF PROVIDER ORG |
| LI81107 | UNAUTHORIZED ERROR WHEN ACCESS TOKEN EXPIRES USING API-MANAGER AND CLOUD-MANAGER WITH OIDC USER REGISTRY |
| LI81136 | SUPERSEDING A PRODUCT FAILS WHEN ATTEMPTING TO DO MULTIPLE TIMES |
| LI81175 | SOME UNICODE CHARACTERS IN JSON REQUEST FAIL THE REQUEST |
| LI81191 | IN PORTAL THE ORGANIZATION SELECTOR MENU DOES NOT WORK IF MANY CONSUMER ORGS ARE LISTED |
| LI81201 | WRONG ERROR MESSAGE WHEN WE DO NOT ALLOW TO SUBSCRIBE FROM APP WHICH CONTAIN DIFFERENT CONSUMER ORG |
| LI81210 | STATIC STATE PARAMETER IN OPENID CONNECT FLOW |
| LI81238 | CLUSTER WASN'T PERSISTING NODE IDS CORRECTLY, SO ACROSS POD RESTARTS FOR MESSAGE QUEUE ISSUES COULD ARISE |
| LI81244 | ORPHANED TRANSACTION LOCKS CAUSE 409 ERRORS WHEN ATTEMPTING TO REMOVE A PRODUCT FROM A CATALOG |
| LI81251 | API IS NOT AVAILABLE DURING PRODUCT REPLACE CAUSING TRAFFIC DISRUPTION |
| LI81252 | ADD ENTITY UPDATE CODE REQUIRED FOR UPGRADES |
| LI81257 | THE MAP POLICY MAY EXHIBIT ADDITIONAL LATENCY FOR SOME APIS |
| LI81264 | UPGRADING THE CLUSTER FAILS TO COMPLETE SUCCESSFULLY |
| LI81270 | PHP VULNERABILITIES |
| LI81273 | SUBSCRIPTION PENDING APPROVAL STATE NOT VISIBLE IN THE DEVELOPER PORTAL |
| LI81275 | ISSUES ENCOUNTERED WHEN EXPOSING AN EXTERNAL API IN THE DEVELOPMENT PORTAL, WITHOUT ENFORCING IN GATEWAY |
| LI81278 | THE APICUP HEALTH-CHECK COMMAND FOR MANAGEMENT SUBSYSTEM MIGHT RETURN ERROR: UNABLE RUN KUBECTL CMD |
| LI81284 | ASSEMBLY ERROR WHEN CREATING A SWITCH WITH OPERATION-ID |
| LI81287 | ARRAY MAPPING FAILS TO MAP CHILD PROPERTIES THE X-IBM-GATEWAY-MAP-EMULATE-V4-EMPTY-JSON-OBJECT IS ENABLED |
| LI81289 | MYSQL VULNERABILITY |
| LI81290 | MYSQL VULNERABILITY |
| LI81291 | ANALYTICS ERROR DATA NOT VISIBLE WITHIN SPACE FOR APIS PUBLISHED TO DATPOWER API GATEWAY TYPE |
| LI81296 | THE "REQUEST.PARAMETERS" VARIABLE FOR FORMDATA PARAMETER DOESN'T WORK PROPERLY AFTER UPGRADE TO 2018.4.1.9 |
| LI81298 | ADD COMMENTS IN SWAGGER EXAMPLE TO PRESENT XS:CHOICE ELEMENTS |
| LI81303 | VALIDATE POLICY INCORRECTLY FAILS XML VALIDATION IN SOME CASES |
| LI81305 | THIRD PARTY OAUTH PROVIDER "CUSTOM HEADER PATTERN" CONFIGURATION DOESN'T SYNC TO DATAPOWER |
| LI81310 | USERNAME/PASSWORD AUTOFILLING IN INVOKE POLICY FIELDS |
| LI81311 | VALIDATE POLICY XML VALIDATION MAY FAIL FOR VALID XML |
| LI81315 | WRONG ID USED FOR POD ANNOTATIONS |
| LI81321 | STRENGTHEN CIPHER SUITES FOR ETCD, KUBE SERVICES, AND CASSANDRA-OPERATOR |
| LI81323 | MAP POLICY ACTION'S DEFAULT PROPERTY DOESN'T ALLOW VARIABLE RESOLUTION FOR INTEGER OUTPUT PROPERTIES |
| LI81324 | GETTING IMPROPER XML RESPONSE FROM DEVELOPER PORTAL UI TRY IT FEATURE |
| 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 |
| LI81336 | IN APIM DESIGNER USER IS UNABLE TO LOAD APIS IN DIRECTORY WITH MISSING X-IBM-CONFIGURATION |
| LI81338 | PRETTY PRINTING CHECK IS NOT WORKING CORRECTLY IN THE 'TRY IT' EXPLORER OF THE API CONNECT DEVELOPER PORTAL |
| LI81341 | DEVELOPER PORTAL ADMIN CONTAINER FAILS TO START AS PIPE FILES ARE DIRECTORIES |
| LI81343 | API PROPERTIES FOR SPECIFIC CATALOGS IN V5 COMPATIBILITY MODE RESPOND WITH THE DEFAULT VALUE RATHER THAN THE SPECIFIC CATALOG VALUE |
| LI81344 | APPLICATIONS ALREADY SUBSCRIBED TO API PRODUCT ARE DISPLAYED AGAIN IN THE SELECT APPLICATION PAGE |
| LI81348 | INCONSISTENCIES WITH THE APPLICATION AND CONSUMER ORGANIZATION DELETE HOOKS |
| LI81356 | 404 ERROR BACK WHEN REMOVAL OF DEFINED POLICY |
| LI81372 | ACCESS_TOKEN FROM APIM TO PORTAL SHOULD BE CACHED |
| LI81373 | MYSQL VULNERABILITIES |
| LI81479 | FULL REFRESH TOKEN SUPPORT FOR API-MANAGER WHEN USING OIDC USER REGISTRY |
| LI81560 | POOR RESILIENCY IN MANAGER/ADMIN UI WHEN WORKER NODE SHUT DOWN |
*** Please 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.
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.
Important notes on upgrading to 2018.4.1.10:
When upgrading to Version 2018.4.1.10, 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.
Starting with IBM API Connect Version 2018.4.1.10, writable LDAP user registries can be used only for onboarding and authenticating Developer Portal users. A writable LDAP user registry cannot be used to authenticate Cloud Manager and API Manager users. If you already have a writable LDAP user registry for use with the Cloud Manager or the API Manager, you must update the registry to be read-only by changing the User Managed property to be false.
Starting with IBM API Connect Version 2018.4.1.9iFix1, after completion of the upgrade, some tasks may have stopped running. See Requirements for upgrading on VMware and Requirements for upgrading on Kubernetes describing action to take.
Finally, a Control Plane file is required if you are upgrading from v2018.4.1.5 or v2018.4.1.6 to v2018.4.1.10 (VMWARE .OVA only). Reference the Upgrade Instructions page in the API Connect IBM Knowledge Center.
Support lifecycle policy for IBM API Connect Version 2018.4.1.10:
IBM API Connect 2018.4.1.10 is fix pack to a Long-Term Supported (LTS) release. API Connect 2018.4.1.10 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 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.10 and the IBM API Connect 2018.4.1.10 Toolkit files can be downloaded from Fix Central :
| Description – Filename | Date Published |
|
IBM API Connect Management V2018.4.1.10 Containers
|
2 March 2020 |
|
IBM API Connect Developer Portal V2018.4.1.10 Containers
|
2 March 2020 |
|
IBM API Connect Analytics V2018.4.1.10Containers
|
2 March 2020 |
|
IBM API Connect Management V2018.4.1.10 for VMWare
|
2 March 2020 |
|
IBM API Connect Developer Portal V2018.4.1.10for VMWare
|
2 March 2020 |
|
IBM API Connect Analytics V2018.4.1.10 VMWare
|
2 March 2020 |
|
IBM API Connect Installation Assist V2018.4.1.10 for Linux®
|
2 March 2020 |
|
IBM API Connect Installation Assist V2018.4.1.10 for Mac
|
2 March 2020 |
|
IBM API Connect Installation Assist V2018.4.1.10 for Windows
|
2 March 2020 |
|
IBM API Connect Toolkit V2018.4.1.10 for Linux®
|
2 March 2020 |
|
IBM API Connect Toolkit V2018.4.1.10 for Mac
|
2 March 2020 |
|
IBM API Connect Toolkit V2018.4.1.10 for Windows
|
2 March 2020 |
|
IBM API Connect Toolkit Designer with Loopback V2018.4.1.10 for Linux®
|
2 March 2020 |
|
IBM API Connect Toolkit Designer with Loopback V2018.4.1.10 for Mac
|
2 March 2020 |
|
IBM API Connect Toolkit Designer with Loopback V2018.4.1.10 for Windows
|
2 March 2020 |
|
IBM API Connect V2018.4.1.10 Analytics.OVA Upgrade File
|
2 March 2020 |
|
IBM API Connect V2018.4.1.10 Management Server.OVA Upgrade File
|
2 March 2020 |
|
IBM API Connect V2018.4.1.10 Developer Portal.OVA Upgrade File
|
2 March 2020 |
| IBM DataPower Gateway for Docker Production Edition v2018.4.1.10 idg_dk20184110.lts.prod.tar.gz |
2 March 2020 |
| IBM DataPower Gateway for Docker Non-Production Edition v2018.4.1.10 idg_dk20184110.lts.nonprod.tar.gz |
2 March 2020 |
|
Kubernetes DataPower Monitor v2018.4.1.10
|
2 March 2020 |
Ensure that you have read and understood the installation instructions for OVAs and Containers before downloading and by using the installation files. You can find detailed installation instructions in IBM API Connect Knowledge Center -- Installing API Connect
IBM API Connect Control Plane for OVA upgrades
When upgrading from v2018.4.1.5 through v2018.4.1.8, on VMWare only, one or more Control Plane files must be downloaded and installed to bring Kubernetes to a supported release level. For more details, see Step 5 of the Upgrade Instructions in the API Connect IBM Knowledge Center.
| Description – Filename | Date Published |
|
IBM API Connect 1.14.0 Control Plane File for OVA (optional)
|
2 March 2020 |
|
IBM API Connect 1.15.0 Control Plane File for OVA (optional)
|
2 March 2020 |
ICP Installation Files for API Connect v2018.4.1.10
| Description – Filename | Date Published |
| IBM API Connect ICP Enterprise V2018.4.1.10 IBM_API_Connect_ICP_Enterprise_2018.4.1.10.zip |
5 March 2020 |
| IBM API Connect ICP Professional V2018.4.1.10 IBM_API_Connect_ICP_Professional_2018.4.1.10.zip |
5 March 2020 |
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 Knowledge Center
| Description – Filename | Date Published |
| IBM API Connect Local Test Environment apic-lte-2018.4.10-50.zip |
16 March 2020 |
Was this topic helpful?
Document Information
Modified date:
27 July 2020
UID
ibm13380055