End of Sale Notice:

F5 NGINX is announcing the End of Sale (EoS) for NGINX Management Suite API Connectivity Manager Module, effective January 1, 2024.

F5 maintains generous lifecycle policies that allow customers to continue support and receive product updates. Existing API Connectivity Manager Module customers can continue to use the product past the EoS date. License renewals are not available after September 30, 2024.

See our End of Sale announcement for more details.

Known Issues

This document is a summary of the known issues in NGINX Management Suite API Connectivity Manager. Fixed issues are removed after 45 days.

We recommend upgrading to the latest version of API Connectivity Manager to take advantage of new features, improvements, and bug fixes.


1.9.0

September 07, 2023

Module crashes when an OpenAPI spec is uploaded with a global security requirement that contains an empty security requirement object

Issue ID Status
44393 Fixed in API Connectivity Manager 1.9.1

Description

API Connectivity Manager crashes when an OpenAPI specification file is uploaded with a global security requirement block containing an empty security object.

Example OpenAPI security requirement with empty security object:

"security": [{}]

1.8.0

July 27, 2023

Cannot use TLS enabled backend with HTTP backend-config policy

Issue ID Status
44212 Fixed in API Connectivity Manager 1.9.0

Description

When configuring a backend-config policy with the transport protocol set to HTTP for an API, if TLS is enabled on that APIs backend, then the configuration will fail with the following error in the API Connectivity Manager log file: “Backend Config policy failed when checking transport protocol match because of: the backend-config policy transport protocol http does not match the proxy backend transport protocol https”


Deployment fails due to duplicate locations

Issue ID Status
43673 Fixed in API Connectivity Manager 1.9.0

Description

When more than one version of an API is published and Append Rule is set to “None”, the deployment fails due to duplicate locations.


Certificates associated with empty instance groups can be deleted, resulting in a broken reference in the API Connectivity Manager module

Issue ID Status
43671 Fixed in API Connectivity Manager 1.9.0

Description

In the Instance Manager Certificates and Keys web interface, you can delete API Connectivity Manager TLS Policy certificates associated with empty instance groups. However, this action may lead to a broken reference problem in the API Connectivity Manager module, resulting in the inability to modify or delete the broken Environment from the web interface.

Workaround

You can delete the Environment using the API if it cannot be modified or deleted using the web interface.


1.7.0

June 21, 2023

Environments with WAF enabled may transition to a Failed status when a Developer Portal cluster is added.

Issue ID Status
43231 Fixed in API Connectivity Manager 1.8.0

Description

If you add a Developer Portal cluster to an environment that has WAF enabled, the environment may transition to a Failed status. If this happens, follow the steps in the workaround.

Workaround

On the Developer Portal:

  1. Open an SSH connection to the Developer Portal and log in.

  2. Install NGINX App Protect.

  3. Stop the NGINX Agent:

    sudo systemctl stop nginx-agent
    
  4. Run the onboarding command to add the Developer Cluster:

    curl -k https://<NMS-FQDN>/install/nginx-agent > install.sh && sudo sh install.sh -g <cluster> -m precompiled-publication --nap-monitoring true && sudo systemctl start nginx-agent
    

    Replace <NMS-FQDN> with the fully qualified domain name of your NGINX Management Suite, and <cluster> with the name of the Developer Cluster.

  5. Confirm the NGINX Agent is started and restart if necessary:

    sudo systemctl status nginx-agent
    sudo systemctl start nginx-agent
    

Resources deployed to a Developer Portal which has had its database reset cannot be updated or removed

Issue ID Status
43140 Fixed in API Connectivity Manager 1.9.0

Description

It is not possible to remove resources from API Connectivity Manager which have been published to a Developer Portal if the Developer Portal database is cleared.


1.6.0

May 11, 2023

Multiple entries selected when gateway proxy hostnames are the same

Issue ID Status
42515 Fixed in API Connectivity Manager 1.7.0

Description

Multiple entries are selected when gateway proxy hostnames are the same.

Workaround

There is no impact to functionality.


The routes filter under the proxy metrics page won’t work with params

Issue ID Status
42471 Fixed in API Connectivity Manager 1.7.0

Description

The routes filter under the proxy metrics page won’t work with params currently.

For example, /api/v1/shops/{shopID}

The API won’t match on the above route.


1.5.0

March 28, 2023

Using policies with targetPolicyName set to anything other than the default value can cause unexpected results.

Issue ID Status
42682 Open

Description

Creating a policy with metadata of “targetPolicyName” set to anything but default can cause issues with secrets being duplicated if more than one policy is created. Setting this value to anything but the default value will also cause the policy to not be applied. The policy may be shown as applied in the UI when it is not.

Workaround

Do not modify the “targetPolicyName” to be anything but the default value.


Array values in token claims are treated as string values

Issue ID Status
42388 Fixed in API Connectivity Manager 1.6.0

Description

When an Access Control Routing match rule targeted a token value that contained an array, the array was collapsed into a comma-separated string. However, the expected behavior is for rules targeting arrays to pass if any value within the array matches the condition, rather than requiring the entire array to match.


Developer Portal: When typing the links to use for the footer, the text boxes keep losing focus

Issue ID Status
41626 Fixed in API Connectivity Manager 1.6.0

Description

The Text to Display and URL boxes on the Developer Portal’s Configure Footer page lose focus when text is being typed.

Workaround

You may need to click back into the boxes several times while typing to regain focus.


TLS setting on listener is not reset when TLS policy is removed

Issue ID Status
41426 Fixed in API Connectivity Manager 1.6.0

Description

When a TLS policy is removed from an environment, the web interface will not automatically adjust the TLS setting on the listener. As a result, the listener will remain in the TLS enabled state, leading to an unsuccessful attempt to save and publish the environment.

Workaround

Toggle the TLS setting in the web interface when removing the TLS policy from an environment.


1.4.0

January 23, 2023

Cluster and Environment deletion issues when Portal Docs are published

Issue ID Status
40163 Fixed in API Connectivity Manager 1.4.1

Description

When a developer portal proxy is hosting API documentation, the infrastructure admin is, in some cases, unable to delete clusters in other unrelated Environments and, therefore, unable to delete those same Environments.


The Proxy Cluster API isn’t ready to be used

Issue ID Status
40097 Fixed in API Connectivity Manager 1.5.0

Description

The API Connectivity Manager API documentation has inadvertently released details of Proxy Cluster endpoints and related policies before their public launch. Consequently, the following Proxy Cluster endpoints and global policies should not be used yet.

The following Proxy Cluster endpoints are not ready for use:

  • /infrastructure/workspaces/{workspaceName}/proxy-clusters
  • /infrastructure/workspaces/{workspaceName}/proxy-clusters/{name}

The following global policies are not yet ready for use:

  • cluster-zone-sync
  • cluster-wide-config

A later version of the release notes will inform you when these endpoints and policies are ready.


Configurations aren’t pushed to newly onboarded instances if another instance is offline

Issue ID Status
40035 Fixed in API Connectivity Manager 1.5.0

Description

When a new instance is onboarded, it will not be configured if any other instances are offline.

Workaround

After onboarding the instance as usual, push the existing configuration again to the new instance, without making any changes.


1.3.0

December 12, 2022

OIDC policy cannot be applied alongside a proxy authentication policy

Issue ID Status
39604 Fixed in API Connectivity Manager 1.4.0

Description

It is not possible to use both an OpenID Connect (OIDC) policy and a proxy authentication policy concurrently.


The web interface doesn’t pass the enableSNI property for the TLS backend policy

Issue ID Status
39445 Fixed in API Connectivity Manager 1.3.1

Description

When configuring a TLS backend policy in the web interface, the new enableSNI property does not match the value of the deprecated proxyServerName property, resulting in an API error. The enableSNI value must be the same as proxyServerName value.

Workaround

Use the NGINX Management Suite API Connectivity Manager REST API to send a PUT request to the following endpoint, providing the correct values for enableSNI and proxyServerName. Both values must match.

Method Endpoint
PUT /infrastructure/workspaces/{{infraWorkspaceName}}/environments/{{environmentName}}


A JWT token present in a query parameter is not proxied to the backend for advanced routes

Issue ID Status
39328 Fixed in API Connectivity Manager 1.4.0

Description

When using JWT authentication with advanced routes, a JWT token that is provided as a query parameter will not be proxied to the backend service.

Workaround

Pass the JWT token as a header instead of providing the JWT token as a query parameter.


1.2.0

October 18, 2022

Developer Portal backend information is unintentionally updated when editing clusters within an environment

Issue ID Status
39409 Fixed in API Connectivity Manager 1.3.1

Description

The Developer Portal backend information may be inadvertently updated in the following circumstances:

  1. If you have multiple Developer Portal clusters and update the backend information (for example, enable TLS or change the host or port, etc. ) for any of those clusters, the update is applied to all of the clusters.

  2. If you have one or more Developer Portal clusters and update any other cluster in the environment (for example, the API Gateway or Developer Portal Internal cluster), the backend settings for the Developer Clusters are reset to their defaults (127.0.0.1/8080/no TSL).

Workaround

  • Workaround for scenario #1

    Use the NGINX Management Suite API Connectivity Manager REST API to send a PUT request to the following endpoint with the correct backend settings for each Developer Portal cluster:

    Method Endpoint
    PUT /infrastructure/workspaces/{{infraWorkspaceName}}/environments/{{environmentName}}

  • Workaround for scenario #2

    If you have just one Developer Portal cluster, you can use the web interface to update the backend settings for the cluster if you’re not using the default settings.

    If you have more than one Developer Portal cluster, use the NGINX Management Suite API Connectivity Manager REST API to send a PUT request to the following endpoint with the correct backend settings for each cluster:

    Method Endpoint
    PUT /infrastructure/workspaces/{{infraWorkspaceName}}/environments/{{environmentName}}


The user interface is erroneously including irrelevant information on the TLS inbound policy workflow

Issue ID Status
38046 Fixed in API Connectivity Manager 1.3.0

Description

On the TLS inbound policy, toggling Enable Client Verification On/Off results in the user interface adding irrelevant information that causes the publish to fail due to validation error.

Workaround

Dismiss the policy without saving and restart the UI workflow to add the TLS inbound policy.


Portals secured with TLS policy require additional environment configuration prior to publishing API docs

Issue ID Status
38028 Fixed in API Connectivity Manager 1.3.0

Description

When the tls-backend policy is applied on a developer portal cluster, the communication between the portal UI and portal backend service is secured. By default, when the portal cluster is created, and the backend is not explicitly specified in the payload, it defaults to HTTP. Adding the tls-backend policy does not automatically upgrade the protocol to HTTPS. If the protocol is not set to HTTPS, publishing API docs to the portal will fail. The user has to explicitly change the backend protocol to HTTPS.

Workaround

In the user interface, navigate to Workspace > Environment > Developer Portal Clusters > Edit Advanced Config. Select “edit the Backend” and toggle the Enable TLS switch to enabled.


A proxy deployed with a specRef field (OAS) and basePathVersionAppendRule set to other than NONE may cause versions to appear twice in the deployed location block

Issue ID Status
36666 Fixed in API Connectivity Manager 1.9.0

Description

If you add an API doc and reference it with the specRef field in the proxy object, the OAS (API doc) is used as the source of truth for the base path. If the OAS (API doc) contains the full correct base path, and you use any basePathVersionAppendRule value other than NONE, the base path will be corrupted by appending/prepending the version in the deployment (e.g. /api/v3/v3).

Workaround

If you are using an API doc with a proxy:

  1. Put the entire true base path of the API in the server section of the API doc:

    Servers:
    - url: https://(API-address)/api/v3
    

    or

    Servers:
    - url: /api/v3
    
    Note:
    In the example above only /api/v3 is relevant for this issue, and it should be the full base path to which the individual paths in the API document can be appended directly.
  2. Set the value of the base path version append rule (basePathVersionAppendRule) in the proxy to NONE.


New users are unable to see pages even though they have been given access.

Issue ID Status
36607 Fixed in API Connectivity Manager 1.3.0

Description

A newly created role needs a minimum of READ access on the LICENSING feature. Without this, the users will not have access to the pages even though they have been granted permission. They will see 403 errors surfacing as license errors while accessing the pages.

Workaround

Assign a minimum of READ access on the LICENSING feature to all new roles


1.1.0

August 18, 2022

To see updates to the Listener’s table, forced refresh of the cluster details page is required.

Issue ID Status
36540 Fixed in API Connectivity Manager 1.2.0

Description

When trying to update the Advance Config for Environment cluster, changes are not reflected on the cluster details page after saving and submitting successfully.

Workaround

Refresh or reload the browser page to see changes on the cluster details page.


Using labels to specify the backend is partially available

Issue ID Status
36317 Fixed in API Connectivity Manager 1.2.0

Description

The targetBackendServiceLabel label is not editable through the web interface. targetBackendServiceLabel is not configurable at the URI level in the spec.

Workaround

targetBackendServiceLabel label can be updated by sending a PUT command to the API.


Ratelimit policy cannot be applied with OAuth2 JWT Assertion policy.

Issue ID Status
36095 Fixed in API Connectivity Manager 1.2.0

Description

Rate limit policy cannot be applied with the OAuth2 JWT assertion policy.


Enums are not supported in Advanced Routing.

Issue ID Status
34854 Fixed in API Connectivity Manager 1.2.0

Description

Enums cannot be set for path or query parameters while applying advanced routing. A list of specific values cannot be specified for their advanced routing parameters.


1.0.0

July 19, 2022

The API Connectivity Manager module won’t load if the Security Monitoring module is enabled

Issue ID Status
39943 Fixed in Instance Manager 2.8.0

Description

If you have Instance Manager 2.7 or earlier installed and attempt to enable both the API Connectivity Manager and Security Monitoring modules on the same NGINX Management Suite management plane, the API Connectivity Manager module will not load because of incompatibility issues with the Security Monitoring module.

Workaround

Before enabling the API Connectivity Manager and Security Monitoring modules, ensure that your Instance Manager is upgraded to version 2.8 or later. Be sure to read the release notes for each module carefully, as they may contain important information about version dependencies.

To see which version of Instance Manager you have installed, run the following command:

  • CentOS, RHEL, RPM-based:

    yum info nms-instance-manager
    
  • Debian, Ubuntu, Deb-based:

    dpkg -s nms-instance-manager
    

Credentials endpoint is disabled by default

Issue ID Status
35630 Fixed in API Connectivity Manager 1.2.0

Description

For security reasons, the credentials endpoint on API Connectivity Manager(ACM) is disabled by default. To use the developer portal credentials workflow, configuration changes need to be made on the ACM host to enable credentials endpoints. Also, communication between ACM and the developer portal can be secured by providing certificates.

Workaround

To enable the credentials endpoints on ACM host

  1. SSH to the ACM host

  2. Enable resource credentials endpoint In {{/etc/nms/nginx/locations/nms-acm.conf}}, uncomment the location block

    #Deployment of resource credentials from the devportal
    #  Uncomment this block when using devportal. Authentication is disabled
    #  for this location. This location block will mutually
    #  verify the client trying to access the credentials API.
    #  location = /api/v1/devportal/credentials {
    #    OIDC authentication (uncomment to disable)
    #    auth_jwt off;
    #    auth_basic off;
    #    error_page 401 /401_certs.json;
    #    if ($ssl_client_verify != SUCCESS) {
    #      return 401;
    #    }
    #    proxy_pass http://apim-service/api/v1/devportal/credentials;
    #}
    
  3. Save the changes.

  4. Reload NGINX on the ACM host: nginx -s reload


Unable to delete an environment that is stuck in a Configuring state.

Issue ID Status
35546 Fixed in API Connectivity Manager 1.2.0

Description

In the web interface, after deleting all of the proxy clusters is an environment that’s in a FAIL state, the environment may transition to a CONFIGURING state and cannot be deleted.

Workaround

Add back the deleted proxy clusters using the web interface. The environment will transition to a Fail state. At this point, you can use the API to delete the proxy by sending a DELETE request to:

https://<NMS-FQDN>/api/acm/v1/infrastructure/workspaces/<infra-workspace-name>/environments/<environmentname>

Installing NGINX Agent on Ubuntu 22.04 LTS fails with 404 Not Found error

Issue ID Status
35339 Fixed in API Connectivity Manager 1.3.0

Description

When installing the NGINX Agent on Ubuntu 22.04 LTS, the installation script fails with a 404 Not Found error similar to the following:

404 Not found [IP: <IP address>]
Reading package lists...
E: The repository 'https://192.0.2.0/packages-repository/deb/ubuntu jammy Release' does not have a Release file.
E: The repository 'https://pkgs.nginx.com/app-protect/ubuntu jammy Release' does not have a Release file.
E: The repository 'https://pkgs.nginx.com/app-protect-security-updates/ubuntu jammy Release' does not have a Release file.

Workaround

Edit the NGINX Agent install script to use the codename focal for Ubuntu 20.04.

  1. Download the installation script:

    curl -k https://<NGINX-INSTANCE-MANAGER-FQDN>/install/nginx-agent > install.sh
    
  2. Open the install.sh file for editing.

  3. Make the following changes:

    On lines 256-258, change the following:

    codename=$(cat /etc/*-release | grep '^DISTRIB_CODENAME' | 
    sed 's/^[^=]*=\([^=]*\)/\1/' | 
    tr '[:upper:]' '[:lower:]')
    

    to:

    codename=focal
    

    —OR—

    Alternatively, on line 454, change the following:

    deb ${PACKAGES_URL}/deb/${os}/ ${codename} agent
    

    to:

    deb ${PACKAGES_URL}/deb/${os}/ focal agent
    
  4. Save the changes.

  5. Run the install.sh script.


OIDC policy cannot be applied on a shared proxy cluster

Issue ID Status
35337 Open

Description

If the same proxy cluster is used for both the Developer Portal and API Gateway, the OIDC Policy is not applied.

Workaround

Within an environment, use separate proxy clusters for the Developer Portal and API Gateway when applying an OIDC policy.


No validation when conflicting policies are added

Issue ID Status
34531 Fixed in API Connectivity Manager 1.3.0

Description

When securing the API Proxy with policies like basic authentication or APIKey authentication, the user is not warned if a duplicate or conflicting policy is already added. Conflicting policies are not validated.

Workaround

Secure the API proxy with only one policy.


CORS policy doesn’t support proxying preflight requests to the backend when combined with an authentication policy

Issue ID Status
34449 Fixed in API Connectivity Manager 1.6.0

Description

On an API Proxy with an authentication policy, applying a CORS policy with preflightContinue=true is not supported.

Workaround

Apply CORS policy and set preflightContinue=false.