Fixes
Explore the fixes for IBM webMethods API Gateway 11.1.0.
Explore the fixes for IBM webMethods API Gateway 11.1.0.
This section provides information about IBM webMethods API Gateway 11.1.0 Fix 1 released in November 2024.
Issue ID | Description |
---|---|
YAI-3679 | The native API’s WS Security policies are not enforced in the outbound call from API Gateway. API Gateway does not honor the policies enforced in the native WSDL, when the native API’s WSDL contains multiple binding WS Security policies and the Outbound Authentication-Message policy is configured in API Gateway. This issue is resolved. |
YAI-38324 | Unable to import an archive with Kerberos settings. Importing an archive with Kerberos settings fails with the error message:“Unable to find KerberosSettings.kerberosSettings Asset KerberosSettings while importing the ACDL file.” This issue is resolved. |
YAI-38357 | When you apply a Traffic Optimization policy to the scope of a SOAP API, the throttling limit is not honored. This issue is resolved. |
YAI-38460 | Importing a port archive with error shown as success. When importing a port with an archive where the ‘pkg’ property is missing, API Gateway incorrectly displays the import as successful, even though the port is not imported. This issue is resolved. API Gateway now adds the default package ‘WmRoot’ if the ‘pkg’ property is missing. In other error cases, the import fails with an appropriate error message. |
YAI-38473 | API status remains active after encountering a StackOverflow Error at startup. At startup, API Gateway activates all APIs. However, if an API encounters a StackOverflow error, the API Gateway UI still displays the API as active. This issue is resolved. Now, if the API encounters a StackOverflow error during startup, API Gateway deactivates it. |
YAI-38594 | API Gateway UI does not display custom gateway endpoints. In some cases, the API Gateway UI does not display custom gateway endpoints for APIs. This issue is resolved. |
YAI-38726 | No validation for OpenAPI files. When you create a new API of type OpenAPI, the source input file is not properly validated for errors, such as invalid references. This issue is resolved. |
YAI-38759 | OpenAPI creation fails with 400 bad request exception. Trying to create an API with an OpenAPI JSON file containing a syntax error fails. This issue is resolved. A new extended setting ‘openAPIImporterValidation’ is introduced to define whether the OpenAPI syntax must be validated before importing the OpenAPI file. |
YAI-38775 | Unable to update a SOAP service using a REST endpoint. When updating a SOAP service through the REST service interface, an internal server error occurs and the stack trace indicates a NullPointerException. This issue is resolved. |
YAI-38827 | When a SOAP native service returns an error with a result payload, API Gateway does not send the response payload if the ‘Send Native Provider Response’ flag is enabled. This issue is resolved. |
YAI-38854 | HTTP Header Field ‘Content-Disposition’ is case sensitive. When creating an API with API Gateway REST API with a multipart/form-data request, this works only if the HTTP header field ‘Content-Disposition’ is sent with case sensitive formatting. This issue is resolved. |
YAI-38102 | The tracer does not work for SOAP APIs when the Validate API Specification is enabled. This issue is resolved. |
YAI-38331 | UI displays incorrect label name. The API Gateway UI displays the label “request.application,claims.CLAIM_NAME” incorrectly. This issue is resolved. The label name has been updated from “request.application,claims.CLAIM_NAME” to “request.application.claims.CLAIM_NAME” with the ‘,’ replaced by a ‘.’. |
YAI-38374 | API Gateway displays an exception when document creation in Elasticsearch fails, but it continues to process the transaction. This issue is resolved. |
YAI-38376 | When API Gateway operates in an environment with the system language set to German, the PreMigrationCheckTask fails during the initial step of the migration process. This issue is resolved. |
YAIC-7056 | After migrating to 11.1, existing keystore assets of type PKCS12 aren’t loaded. It is also not possible to create a new keystore asset of type PKCS12, because it fails to load. This issue is resolved. |
YAI-38263 | Selecting a Gateway scope when promoting assets in API Gateway results in a DataStoreException. This issue is resolved. |
YAIC-6959 | In the Analytics page, View event with payload screen does not display the payload when the payload size is more than 5 mb. This issue is resolved. |
YAIC-6904 | Determining the proper SOAP operation from the SOAP envelope caused an issue. This issue is resolved. |