API Portal 7.7 March 2021 Release Notes
6 minute read
API Portal is available as a software installation or a virtualized deployment in a Docker container. For more information, see the following options:
- If you are installing API Portal for the first time using this update, see Install API Portal.
- If you are already using API Portal (7.5.x, 7.6.x, 7.7.x) and want to install this update, see Upgrade API Portal.
- You can use the cumulative upgrade script to upgrade directly from earlier versions (for example, 7.5.5, 7.6.2) to API Portal 7.7 November, then apply this update package to update your API Portal to the March 21 release.
- See API Portal single version upgrade to upgrade versions incrementally.
- To deploy API Portal in Docker containers, see Deploy API Portal in containers.
- If you are already using API Portal in Docker containers and you want to install this update, see Upgrade API Portal in Docker containers.
New features and enhancements
Unattended mode enhanced to use a configuration file for parameters
API Portal unattended mode can use up to 24 parameters, all of which must be specified on the command line. From this update, this was made easier. You can specify the parameters in a configuration file by using the
--optionfile parameter with API Portal
uninstall scripts. For more information, see Unattended installation.
You can also watch How to use a configuration file for simpler installations (unattended mode) demo video on Axway API Management YouTube chanel.
- New module allowing easy integration with Intercom to enable chat support on API Portal.
- Microsoft Edge browser is now supported.
- New Axway icons, color palettes, and typography were incorporated.
- The name of the relevant API Manager instance is now displayed on the API catalog (on Grid and List view layouts) and in the API details page.
- A new notification has been added to alert the organization administrator to review applications that are pending approval.
- Labels and values for custom properties are now translatable.
Limitations of this update
This update has the following limitations:
- API Portal 7.7.20210330 is compatible with API Gateway and API Manager 7.7.20210330 only.
- To upgrade from earlier versions (for example, 7.5.5, 7.6.2) you must first upgrade to API Portal 7.7 only.
- This update is not available as a virtual appliance or as a managed service on Axway Cloud.
There are no major changes in this update.
As part of our software development life cycle we constantly review our API Management offering. In this update, the following capabilities have been deprecated:
- Internet Explorer 11 and earlier versions are no longer supported. Microsoft Edge is recommended.
- API Portal 7.7 January 2020 update is end of support (EOS).
No capabilities have been removed in this update.
This version of API Portal includes:
- Fixes from all 7.5.5, 7.6.2, and 7.7 service packs released prior to this version. For details of all the service pack fixes included, see the corresponding SP Readme attached to each service pack on Axway Support.
- Fixes from all 7.7 updates released prior to this version. For details of all the update fixes included, see the corresponding release note for each 7.7 update.
Fixed security vulnerabilities
|Internal ID||Case ID||CVE Identifier||Description|
|IAP-4003||Issue: Swagger IO is using vulnerable version of marked library. Resolution: Marked library is upgraded to a safer version.|
|IAP-3842||Issue: API Portal is using vulnerable version of Axios library. Resolution: Axios library is upgraded to a safer version.|
|IAP-4077||Issue: PHP version in Ready Made Docker image was 7.4.14, which was vulnerable when using SOAP extension for connecting to a SOAP server. Resolution: PHP version in Ready Made Docker image was upgraded to 7.4.16.|
Other fixed issues
|Internal ID||Case ID||Description|
|IAP-3940||1228612||Issue: API description is not shown on API Catalog. Resolution: API summary is shown as description by default.|
|IAP-3949||1229842||Issue: When hide tags from API Catalog page is enabled, they are not hidden in create and edit application pages. Resolution: New configuration is added for applications which allows to hide tags from applications pages.|
|IAP-4000||Issue: While creating application from an API Details page, the user can see a list of all available organizations, to some of which the API is not connected. Resolution: When an application is being created from an API, the user see a list of the organizations to which the API is assigned.|
|IAP-4002||1231371||Issue: The documentation was not clear on what resources are recommended for use for Docker artifacts released before November. Resolution: All documentation sections have been updated to link to the latest docker artifacts recommended for production.|
|IAP-4033||Issue: Redirect after login option in JAI is not working when multiple languages are installed. Resolution: Redirect after login option in JAI works for multiple-languages API Portal instances.|
|IAP-4054||01229501||Issue: HEAD method is allowed for the request that validates the registration. Resolution: Only GET method is allowed for the request that validates the registration.|
|IAP-4055||1232846||Issue: PHP CLI version is checked from the context of the user who is running the installation while it’s used in the context of the Apache user. Resolution: Run
The following are known issues for this update.
When Multi Manager feature is configured, API Portal users are no longer able to login
After a recent bug fix in API Manager (RDAPI-20021), the
Authenticate to Master policy is no longer working after upgrading from releases earlier than API Portal July 2020. To fix this, perform the following steps:
- Open all slave managers configurations in Policy Studio, and click to Edit the
- Click the Login to Master (Connect to URL) filter, and enter
Accept: */*for the Request Protocol Header.
- Click the Enter key twice to create two blank lines after
Alternatively you can take the updated
AuthenticateToMaster policy and apply again your configurations.
Page layout and alignment for Arabic language
Changing the API Portal language to Arabic (or any other right to left language) results in issues with page layout and alignment on the API Portal Home and Pricing pages, and some buttons are not visible. As a workaround, you can turn on the development mode in JAI. Follow these steps:
- Log in to Joomla! Admin Interface (JAI).
- In the JAI top navigation bar, click Extensions > Templates.
- Click your template style (for example,
purity_III * Default) to open it.
- Click the General tab.
- Change Development Mode to
- Click Save and click Close to close the template style.
Related Issue: IAP-308
There are no major changes in this update.
To find all available documentation for this product version:
- Go to Manuals on the Axway Documentation portal.
- In the left pane Filters list, select your product or product version.
Customers with active support contracts need to log in to access restricted content.
For information on the different operating systems, databases, browsers, and thick client platforms supported by each Axway product, see Supported Platforms.
The Axway Global Support team provides worldwide 24 x 7 support for customers with active support agreements.
Email firstname.lastname@example.org or visit Axway Support.
See Get help with API Gateway for the information that you should be prepared to provide when you contact Axway Support.