API Manager 2.x Release Notes
API Manager release notes include information about changes, new features, improvements, and resolved issues in releases of API Manager.
2.5.9
November 12, 2024
-
Now, when the first request from a Mule API Gateway to API Manager is performed for a particular API, API Manager makes an initial setup with the provided information.
NOTE: If additional requests are received for the same API during this setup, the Gateway will receive a 429 error status. -
The Service Mesh End Of Life creation blocker is now active.
-
Customers without a CloudHub entitlement cannot deploy proxy applications through API Manager.
2.5.7
October 31, 2024
-
Service Mesh is scheduled for End of Life on May 21, 2025. To integrate your micro services with Anypoint Platform, use Flex Gateway instead.
2.5.6
October 30, 2024
What’s New
-
The automated policy list is now shown in order of application.
Fixed Issues
Issue Resolution |
ID |
The API list now shows the correct states for Flex Gateway APIs. |
W-17015895 |
2.5.5
October 16, 2024
What’s New
-
You can now view more owners by default on the Client Applications page.
-
You can now apply policies to APIs deployed to Flex Gateway, even if the Gateway version is unknown (because no replicas are connected).
-
You can now see APIs with multiple upstreams in the Project View.
-
You can now create self-managed server APIs using the API wizard.
-
You now see a notification for API Manager 1.x end of life on organizations that have unclassified APIs.
-
You can now use both internal and external client providers within the same environment at the same time.
For more information, see Configure Multiple Client Providers for Client Management.
2.5.4
October 7, 2024
What’s New
-
Now, when deploying an API with policies to Flex Gateway for the first time, policy implementations are pinned.
-
Now, if a user attempts to change the Flex Gateway version where an API is deployed, and one of the applied policies is not compatible with the new target, the operation is rejected.
-
Now, When changing the Flex Gateway version, if an Automated Policy currently covering the API is lost, the user is now warned and can choose to either proceed or cancel the operation.
2.5.3
October 1, 2024
What’s New
-
You can now see HTTP API instances in Governance reports, as well as AsyncAPI and REST API instances.
-
API Manager now includes a header
x-request-d
to include the internal trace ID. -
Email URL functionality for contracts generated in API instances within sub-organizations is now operational.
-
You can now apply different versions of the same policy to various resources within the same API instance.
-
API instance SLA Tier limits are now validated to ensure that
maximumRequests
andtimePeriodInMilliseconds
are integers. -
You can now see the SLA Tier in the client application page for APIs from environments.
-
Now, only users with environment or organization credentials are able to export API instances policies with sensitive fields.
Fixed Issues
Issue Resolution |
ID |
You can now see new implementations when using the Check for implementation updates button for automated policies. |
W-16619577 |
2.5.2
August 27, 2024
What’s New
-
The API Key Metrics experience receives frequent updates. To ensure uninterrupted access, verify that Anypoint Monitoring is enabled:
-
CloudHub 2.0 and Runtime Fabric applications: Anypoint Monitoring is enabled by default.
-
CloudHub applications: Configure Anypoint Monitoring. See Setting Up Monitoring for CloudHub Deployments.
-
Hybrid Runtime applications: Install the Anypoint Monitoring Agent. See: Setting Up Monitoring for Hybrid Deployments.
-
2.5.1
August 23, 2024
What’s New
-
Mule API Analytics will soon be replaced by Anypoint Monitoring. Start transitioning to Anypoint Monitoring to monitor APIs effectively. Contact your MuleSoft representative for more information.
-
Audit logs now include a trace id.
Fixed Issues
Issue Resolution |
ID |
Modifying an API label for a hybrid proxy application now correctly updates the existing proxy application. |
W-15838700 |
Users without FlexGateway entitlement are now able to publish split model custom policies. |
W-16496236 |
2.5.0
July 11, 2024
What’s New
The following endpoint responses now include fewer fields, and the responses include no sensitive information:
For information about which fields are now included in the responses for these endpoints, see the API Manager API documentation.
2.4.30
June 11, 2024
What’s New
-
API Manager now limits the number of API Groups, API Group Versions, and API Group Instances per business group. Each business group can have a maximum of:
-
1200 API Groups
-
1200 API Group Versions
-
2000 API Group Instances
-
-
This release contains accessibility improvements.
Fixed Issues
Issue Resolution |
ID |
Deploying an API proxy for the first time with an old policy implementation version now succeeds (and no longer returns HTTP status code 500). |
W-15945517 |
2.4.29
May 22, 2024
What’s New
-
When multiple Mule gateways are connected to the same API instance, API Manager now saves the highest gateway version.
-
This release contains accessibility improvements, including additional focus indicators and fixes for some contrast color issues.
Fixed Issues
Issue Resolution |
ID |
Policy incompatibilities are now calculated each time rather than only when the runtime or java version changes. |
W-15467066 |
The correct Java version is now shown when creating Mule APIs. |
W-15578441 |
2.4.28
April 12, 2024
What’s New
The following API Manager permissions are now available in Access Management:
-
Manage Client Applications: Enables users to create and manage client applications in the root organization. Users with this permission can view and modify application credentials and can add and remove client owners.
-
View Client Applications: Enables users to view client applications in the root organization. Users with this credential cannot view an application’s secrets and cannot modify applications.
2.4.27
February 29, 2024
Fixed Issues
Issue Resolution |
ID |
When editing APIs, Save & Apply is now disabled for users that don’t have the edit API permissions. |
W-15040213 |
When configuring a new hybrid API instance in an environment where only Mule 3 targets are present, you can now select a Mule 3 target. |
W-15102034 |
2.4.26
February 15, 2024
Fixed Issues
Issue Resolution |
ID |
When you promote a Hybrid API instance to a new environment, the API Summary now renders correctly. |
W-15030396 |
2.4.25
February 7, 2024
What’s New
-
You can now upgrade your policies and API proxies to Java 17. See Upgrading Policies and Upgrading API Proxies.
Fixed Issues
Issue Resolution |
ID |
When applying a resource-level policy to specific methods of the API instance, the URI template regex field no longer shrinks when you select multiple Method values. |
W-14802785 |
When you promote a Hybrid API instance to a new environment, the API instance classification remains Hybrid and is no longer reclassified to Standalone. |
W-14829827 |
2.4.24
January 24, 2024
Fixed Issues
Issue Resolution |
ID |
When applying an automated policy, the Rule of application selection now renders correctly. |
W-14853129 |
2.4.23
December 6, 2023
What’s New
-
Resource-level configuration options are no longer shown when applying a policy that does not support resource-level configurations.
-
The UI is now improved for accessibility by including the addition of alternative text for images, and alternative visual and non-visual indicators.
-
A warning is now displayed when policies are incompatible with the API runtime version.
Fixed Issues
Issue Resolution |
ID |
API Manager now properly redirects pre-crowd customers. |
W-13783748 |
2.4.22
October 27, 2023
What’s New
API Manager now supports space selection for Mule API Proxies deployed to CloudHub 2.0.
2.4.21
October 17, 2023
What’s New
API Manager now supports Anypoint API Governance conformance reports for governed API instances.
+ To learn more about governing API instances, see:
2.4.20
October 10, 2023
What’s New
-
Mule 4.4.x is now the default version for API proxies deployed to CloudHub, CloudHub 2.0, and Runtime Fabric.
-
For API instances deployed to CloudHub 2.0, the space name is now visible in the API Settings.
-
You can now dismiss Mule 3 end of life notifications for 14 days.
-
For API instances deployed to Flex Gateways version 1.5.0 or later, API Manager automatically sets the upstream’s Weight to 100% and disables the field when only one upstream service exists for that route. Adding an additional upstream to the route enables you to configure the upstream Weight.
-
This release contains accessibility improvements in the UI, including the addition of alternative text for images and alternative visual and non-visual indicators.
Fixed Issues
Issue Resolution |
ID |
For Flex Gateway HTTPs API instances sharing the same port, if one of the instances has an inbound TLS context applied, leaving the inbound TLS context blank for additional instances applied to the same port does not result in an error. |
W-14162848 |
2.4.19
August 23, 2023
What’s New
-
For requests made from Connected Apps, API Manager Audit logs now include the Connected App’s name and ID.
-
The Mule API Analytics tab is now visible to users with
View APIs Configuration
permission. -
Some error messages are now improved for clarity.
2.4.18
August 7, 2023
What’s New
-
External Bad Request (
400
) errors do not convert to Bad Gateway (502
) errors. -
This release contains accessibility improvements in the UI, including the addition of alternative text for images and alternative visual and non-visual indicators.
Fixed Issues
Issue Resolution |
ID |
You can now apply Mule 4 custom policies uploaded to Exchange via Maven as automated policies in an environment without APIs. |
W-12369588 |
2.4.17
July 20, 2023
What’s New
-
API Manager now supports API instances with multiple upstream services for Flex Gateway running in Connected Mode.
For more information, see Multiple Upstream Services for Flex Gateway Running in Connected Mode.
-
Deployments to deprecated Flex Gateway versions are now blocked.
For information about Flex Gateway version support, see Product Versioning and Back Support Policy
-
This release contains accessibility improvements in the UI, including the addition of alternative text for images and alternative visual and non-visual indicators.
Fixed Issues
Issue Resolution |
ID |
Autocomplete for the Upstream URL field now works correctly. API Manager now only autocompletes the field when the page is first loaded and only if the information is available. |
W-13735853 |
The Client provider field now shows the correct provider when editing an API instance. |
W-13768260 |
2.4.16
July 3, 2023
What’s New
-
When adding a new API instance, there are now separate pages for the upstream and downstream configuration settings.
-
When editing an API instance from the settings page, there are now separate sections for the upstream and downstream configuration settings.
2.4.15
June 6, 2023
What’s New
-
Selecting an API instance from API Administration now navigates you to the new API Summary page instead of the API Settings page. The API Key Metrics and the API instance information such as the type, API version, and API instance ID now appear on the API Summary page. Only the runtime and endpoint configuration still appear on the Settings page.
-
In API Administration, the Analytics tab is now Mule API Analytics.
2.4.14
May 23, 2023
Fixed Issues
Issue Resolution |
ID |
The API Instance field now appears correctly when filtering client applications with Datagraph contracts. |
W-12964876 |
2.4.13
May 10, 2023
Fixed Issues
Issue Resolution |
ID |
API Manager now correctly shows disabled policies. |
W-13030137 |
2.4.12
April 14, 2023
What’s New
-
Connected Apps can create and manage client applications. For more information, see Creating Client Applications with the Connected App Feature.
-
API status is now shown as active only when deployment is successful.
-
API Manager uses a standalone replica list to report configuration status based on the version of each connected replica.
Fixed Issues
Issue Resolution |
ID |
When a deployed API instance with policies applied is deleted, the policies are also deleted. |
W-12779232 |
2.4.11
March 28, 2023
What’s New
You can deploy Mule Gateway proxy applications directly to CloudHub 2.0.
Fixed Issues
When applying policies to non-REST APIs, policies only applicable to REST APIs are not visible.
2.4.10
February 22, 2023
What’s New
For Flex Gateway running in Connected Mode, API Manager now supports:
-
Policy execution order
For more information, see Reordering Policies.
-
TLS and mTLS context configuration
For more information, see Configuring TLS Context for Flex Gateway in Connected Mode.
2.4.9
January 18, 2023
What’s New
For API Instances, the Implementation URI and Consumer endpoint fields now:
-
Validate if the specified URL is a valid URL.
-
Support parameterization using
{}
,<>
, or<<>>
.
2.4.7
November 2, 2022
What’s New
The API Header on the settings page is improved for a better experience:
-
The API actions are now inside the Actions button in the page header title.
-
The API header is now only informative. The content in the API header is not editable, and the edit buttons were removed. The API instance label and API consumer endpoint fields editable in the API header are now only editable in the Endpoint configuration section following the API header.
-
For Mule 4 APIs, since the auto-discovery ID is the same as the API instance ID, the auto-discovery ID was removed for clarity. The API Manager docs are updated to highlight this change and instruct users where to find the API instance ID.
-
The API notification messages are now displayed at the beginning of the API header.
2.4.6
October 17, 2022
What’s New
Mule 3.8 and 3.9 EOL messages are shown in API Manager for:
-
APIs running on Mule 3.8, which has already reached end of life and whose extended support ended on November 16, 2021.
-
APIs running on Mule 3.9, whose standard support ended on March 20, 2021.
Improved user experience over Flex 1.2.0 new features:
-
Adding port sharing validation.
2.4.5
September 28, 2022
What’s New
Flex Gateway information shown in API Manager has been enhanced as follows:
-
Flex Gateway data representation on API Manager charts is improved.
-
Message logs can now be viewed and downloaded in order from latest to oldest.
-
The message log streaming information now specifies log level, such as Info, Warn, and Error.
2.4.4
August 25, 2022
What’s New
The SLA Tiers, Contracts, and Client applications sections are improved for a better experience:
-
For SLA Tiers, the delete and deprecate actions are now found in the context menu at the end of each tier.
-
For Contracts:
-
The Pending tier change status is now named Approved (pending tier change). The current tier and requested tier can now be edited using the pencil icon without opening the application detail information.
-
The text in the column now changes from N/A to - when there is no current tier or requested tier.
-
The Refresh functionality is now added.
-
-
For Client applications:
-
The Pending contract column now shows the amount of pending contracts for each application.
-
Owners are now shown by email and not by name.
-
The Pending tag is now added to the drop-down options for APIs, API versions, API instances, group, group versions, and group instances to search for pending contracts easily.
-
Fixed Issues
-
For Contracts:
-
The Status filter now considers all contracts for the api and not just the contracts shown in the current view.
-
The Requested SLA tier can now be changed when a contract is in the Approve (pending tier change) status.
-
2.4.3
July 29, 2022
What’s New
-
API Manager now notifies you when policy implementations are incompatible with your current Flex Gateway version.
-
Applying a Message Logging policy to your API instance in API Manager allows you to view basic message logs for APIs managed by Flex Gateway within API Manager.
2.4.2
July 28, 2022
What’s New
-
You can now sort by the Error Rate and Total Requests columns in the API Manager API Administration page.
2.4.0
May 2, 2022
MuleSoft announces the release of API Manager 2.4.0.
New Features and Enhancements
The following new features and enhancements are introduced in API Manager 2.4.0:
-
You can now manage Flex Gateway APIs.
-
The new API Wizard introduces a streamlined way to create APIs.
-
Policy and automated policy management have been improved.
-
The release introduces a new way to create custom policies for Mule 4 and Flex Gateway.
-
The behavior of some policies has changed. For example, The IP Allowlist and IP Blocklist policies no longer accept a comma-separated list. The policies now accept data formatted as an array.
For details, see Anypoint API Manager.
2.3.0
August 12, 2021
MuleSoft announces the release of API Manager 2.3.0.
New Features and Enhancements
The following new features and enhancements are introduced in API Manager 2.3.0:
-
The API list view has been redesigned to enable quick glances at important information, without having to click into specific API instances.
-
In the redesigned API list, you can now view total requests and error rates for an API (for the previous 24 hours).
For details, see What Anypoint API Manager Is.
2.2.16
June 4, 2021
This release introduces the following enhancement:
-
Enhanced the UI to have the Mule 4 version selected by default for APIs.
-
Fixed bugs and implemented security improvements.
2.2.14
May 30, 2020
This release introduces platform-wide support for API Groups across API Manager, Exchange, and API Community Manager, enabling you to package multiple API instances into a single cohesive unit for your API consumers.
API consumers can access the published API Groups from Anypoint Exchange and API Community Manager. For more information about this feature, see API Groups.
2.2.13
April 02, 2020
This release introduces support for multiple identity providers for client management. You can now assign different client identity providers to business groups, environments, and APIs.
Configuring multiple client providers enables you to enforce security and regulations in your business organization.
For more information about this feature, see Configuring Multiple Client Providers.
2.2.12
October 5, 2019
This release provides this new feature:
-
Support for WSDL and RAML payload validations for Mule 3 and Mule 4 proxy applications.
See API Proxy Validations for more information.
2.2.11
May 4, 2019
This release provides this new feature:
-
Improved UI modal for changing Mule 3 custom policy version.
See Change a Custom Policy Version for Mule 3 for more information.
2.2.9
Jan 26, 2019
This release provides this new feature:
-
Automated policy for Mule 4 APIs
-
Adding RAML support for "Create new API"
-
While creating an API instance, API version and asset version are prepopulated
-
When deploying Mule 4 to CloudHub it is possible to choose specific runtime version
-
Notification for a managed API if API spec changes or newer version available in Exchange
2.2.6
November 3, 2018
This release provides this new feature:
-
API Manager 2.x users will get access to Secrets Manager.
-
Configure, secure & deploy HTTPs proxies using certificates (keystore/truststore) stored in Secrets Manager. This feature will be available for Mule 4 APIs deployed to CloudHub & Hybrid deployment targets.
2.2.5
August 30, 2018
This release provides this new feature:
-
User-defined ports for CloudHub deployments
-
Added "Manage Runtime Fabric" proxy link
-
Auto populate implementation URI from Exchange
-
Support for Analytics chart to every granular permission
2.2.3
June 2, 2018
This release provides this new feature:
-
Changes in platform APIs for unclassified environments to facilitate CI/CD pipelines.
2.2.2
May 17, 2018
This release provides these features:
-
Fine-grained access control for the November release of API Manager 2.0.
-
Logging and Header injection and removal policy for 3.8.5+ runtimes.
-
On the API Settings page "Client Applications" has been renamed to "Contracts".
-
Bug fixes.
Fixed in This Release
-
Bug when displaying client ID enforcement details. (AP-3976)
-
Exporting a Mule 4 API containing a policy resulted in a "TypeError: Cannot read property" message. (AP-3941)
-
If a valid URL with OAuth was copied from API Manager, and the user then logged out, subsequent attempts to access the URL failed with an NPE. (AP-3907)
-
Redeploy button incorrectly disabled after a deploy. (AP-3955)
-
When a user only has Asset Admin permission in Anypoint Exchange, the action of making the API Instance public or private fails. (AP-3860)
-
Allow updating these fields, which were set to read-only after the November upgrade: api.name, api.groupId (also updates the apiversion.groupId), api.assetId (also updates the apiversion.assetId), and apiversion.name. (AP-4020)
2.2.1
April 23,2018
This release includes these improvements and bug fixes.
-
Support for 3.9 proxies.
-
Fixes an issue when approval email was not sent after requesting access for published APIs with manual approval.
-
Fixes an issue with autocomplete on import from Exchange.
-
Improved error message when deleting Client Applications with OKTA as the IM provider.
-
When autodiscovery looks for API ID that does not exist, Platform returns 403 instead of 404.
2.2.0
January 27, 2018
This release supports deployment for Mule 4.1.0 proxies on the November release.
2.0.0
November 18, 2017
This release of API Manager includes new and enhanced features for accounts that have upgraded to the November release. If your account hasn’t been upgraded yet, please contact your Customer Success representative.
Key Changes and Enhancements
-
A tight integration of Anypoint Platform components extends the use of environments to API management.
-
API permissions are now environment-based.
-
You can now create multiple instances of an API.
-
APIs in Exchange can be managed from API Manager.
-
There are two new APIs for managing APIs:
-
API Manager API v1.0 to manage API.
-
API Manager proxy API v1.0 to manage deployment of API proxies through API Manager.
-
-
Support for Mule 4 Early Access. Mule 4-related changes to API Manager are:
-
Classloader isolation exists between the application, the runtime and the connectors, and policies.
-
This release of Mule 4 changes the packaging, size, and scope of a policy.
-
All policies are non-blocking.
-
All policies except CORS, which is executed first, can be ordered.
-
-
Custom policy development has changed.
-
Header propagation no longer occurs by default and needs to be configured.
-
Resource level policy support, which was restricted to RAML-based APIs, is extended to any HTTP API.
Changes Related to Using Mule 4 Early Access
-
API Manager does not support auto-generation and deployment of proxies.
-
The Throttling policy is not supported in this Mule release.
-
Mule 4 replaces the security manager policies with two HTTP Basic Authentication policies:
-
A combination of HTTP Basic Authentication and Simple Security Manager
-
A combination of HTTP Basic Authentication and LDAP Security Manager
The policy protects an API by expecting and validating a user name and password.
-
-
You can configure the Rate Limiting policy if the quota is shared among the cluster nodes or not. By default, the quota is shared among the cluster nodes.