June 26, 2026

To:         Layer7 API Developer Portal  Customers

From:     The Broadcom Layer7 Product Team

Subject:  General Availability Announcement for Layer7 API Developer Portal 5.4.2

The Layer7 product group of Broadcom's IMS division is pleased to announce that the Layer7 API Developer Portal 5.4.2 is now available. This release delivers key enhancements across API management usability, infrastructure operations, security, and global developer experience based on customer feedback. 

Congratulations to the team for reaching this important milestone and for continuing to deliver value to our customers.

Here are the highlights of this Layer7 API Developer Portal release:

• Infrastructure Management & Gateway Version Control — Infrastructure Management adds centralized visibility and control over Gateway patch levels and software versions, supporting Monthly Platform Patches (MPP), Monthly Software Patches (MSP), and minor version upgrades for OVA-based Gateways. The Portal manages the full upgrade sequence with real-time per-node progress tracking directly from the Admin Console. 
• Gateway Registration — A unified Gateway registration model that spans three operational domains: API Management, Infrastructure Management, and Intelligence is now provided. A single Gateway registration controls which management capabilities are active, eliminating duplicate registration steps. Previous references to “Proxies” had now moved to “Gateways” in the UI.
• API Revision History — The Portal now automatically tracks revisions (20 by default) for every API edit, capturing changes to details, tags, custom fields, and policy entities. Publishers can mark specific revisions as permanent snapshots to protect them from rolling deletion, and can restore an API to any previous revision with a single click.
• API Page Redesign — The legacy wizard-based API create and edit flow has been replaced with a modern, tab-based layout. Publishers can jump directly to specific configuration areas such as Overview, Spec, and Config without stepping through a wizard.
• GraphQL Endpoint: Application Management — Building on the GraphQL CRUD capabilities introduced for APIs in Portal 5.4.1, the /graphql endpoint now supports full Application management. API consumers and automation engineers can retrieve, create, update, and delete Applications — including nested entities such as API Keys, Custom Fields, Products, and Certificates — in a single request instead of multiple sequential REST calls.
• Multi-Language Support Expansion — The API Portal's multi-language capabilities now extend to OpenAPI Specification/Swagger files, email notification templates, and API documentation. 
• API Publishers can associate language-specific Swagger files with a single API, and the Portal automatically serves each developer the documentation matching their active locale. 
• Email templates can be authored in multiple languages and are delivered based on the recipient's user profile locale. 
• API documentation can now be authored and managed in multiple languages directly in the Admin Console
• Centralized Feature Flag and Settings Management — Feature flags and platform settings previously accessible only through PAPI are now discoverable and manageable directly in the Portal Admin Console. Settings are organized into contextual categories (API Settings, General, Email/SMTP) and each flag includes plain-language descriptions, dependency requirements, and impact indicators.
• Global Quota Limits for Portal Endpoints — A new identity-aware global quota system protects all Portal endpoints against brute-force attacks and resource exhaustion. Limits track by authenticated user identity or by IP address for unauthenticated requests.
• Audit Logging: Source IP Address Capture — Every audit record now includes the source IP address of the originating request, with support for load-balancer header passthrough to preserve the original client IP in proxied environments. A new IP Address filter in the Audit Logs page allows security and compliance teams to quickly isolate all actions from a specific source.
• Apache Kafka for External Gateway Message Routing — Apache Kafka replaces RabbitMQ as the default message broker for new Gateway deployments, providing higher throughput, fault tolerance, and improved scalability across distributed environments. Existing proxies retain RabbitMQ routing by default and can be migrated to Kafka on a per-proxy basis.
• Visibility into Not Deployed Entities — The "Not Deployed" counts on Gateway Details and Key Store Details pages are now clickable links that navigate directly to a filtered list of undeployed APIs or API Keys, including names, statuses, and creation dates. This eliminates the need to manually search for orphaned or failed entities.
• Configuring New User Registration Emails — The Portal can now be configured to send automated email notifications to designated roles each time a new user registers, eliminating the need to manually poll the Admin Console for pending access requests. Digest reporting is also available via User Settings.
• Application Lookup by API Key — The Applications List page now accepts an API key as a direct search input, returning the associated application immediately. A “Go To Key” option navigates directly to the specific API key record within the owning application, reducing troubleshooting time when logs reference an API key without an application name.
• Automated Cleanup of Processed Request Objects — A scheduled daily job automatically removes approved and rejected workflow request records older than a configurable retention period (default: 365 days). Pending requests are never deleted. The cleanup can also be triggered on demand via PAPI for pre-maintenance housekeeping.
• Remote Key Store Support for GemFire — GemFire is now supported as a remote key-value storage backend for API keys, joining the existing Redis support. Organizations standardizing on GemFire can consolidate their caching infrastructure, and the Portal supports mixed proxy environments where some proxies use Redis and others use GemFire simultaneously.

End of Support Notice

Please take note of the following:

• API Hub Deprecated — Following the expansion of multi-language support in the API Portal UI, the legacy API Hub is now in maintenance mode. No new features or enhancements will be added. The API Hub is subject for removal as soon as the next Portal release. External API Hub implementations registered with the Portal may continue to be used.
• RabbitMQ Deprecation Planned — Apache Kafka is now the designated default message broker for all new Gateway deployments. RabbitMQ remains supported for existing proxies via the useRabbitMQ toggle. Customers should begin planning the migration of existing proxies to Kafka ahead of the scheduled RabbitMQ deprecation.
• Portal Authorization API — All endpoints in the legacy Portal Authorization API are deprecated and will be removed in an upcoming release. Please use the Roles and Permissions API to manage Roles and Permissions.
• API Plans and API Groups Deprecated — As announced previously with the Portal 5.3.1 release, both API Plans and API Groups are deprecated in favor of API Products. While these will not be removed immediately, it is important to evaluate your use of API Plans and API Groups and work with Broadcom to identify any blockers that may prevent the migration to API Products.

For a complete list of enhancements, changes and deprecated capabilities, please see the release notes, deprecated features, and product documentation for more information.

NOTE: The Broadcom private repository for Helm images will be updated with the release artifacts soon. Once available, the ability to get an access token will be enabled on the Broadcom Support download site.

You can download your copy of Layer7 API Developer Portal 5.4.2 from Broadcom Support Online https://support.broadcom.com/. If you have any questions or require assistance please contact Broadcom Customer Care online at https://www.broadcom.com/support/software/contact where you can submit an online request using the Customer Care web form: https://ca-broadcom.wolkenservicedesk.com/web-form?_ga=2.205828371.1432263889.1590607313-713014253.1588711301 .  You can also call Broadcom Customer Care at +1-800-225-5224 in North America or see https://www.broadcom.com/support/software/contact for the local number in your country. 

Should you need any assistance, our Broadcom Services experts can help.  For more information on Broadcom Services and how you can leverage our experience, please visit https://www.broadcom.com/support/ca/services-support/ca-services.

Your success is very important to us, and we look forward to continuing our successful partnership with you.

To review Broadcom Support lifecycle policies, please review the Broadcom Support Policy and Terms located at: https://support.broadcom.com/.  

Thank you again for your business.